:+1: the issues that are important to you!

[ruben-arts]

Figuring out which issues are the most important is hard for an open source project.

The best way to measure this is by tracking the 👍 on a issue. So please leave one on the issues you care about!

How to get a speedy fix on your issue

1. 💯 Do it yourself, we motivate and welcome contributions!
   • If you add a test/test-plan that fails without your change and works afterwards, then your PR will probably be merged quickly!
   • We like to help people learn Rust, so don't worry about your programming skills.
2. 🤩 Have a proper reproduction of the issue with a minimal example.
   • Include the pixi.toml and pixi.lock when you can. Simplify the file to the least amount of lines where the issue comes up.
   • Include the commands you ran in the terminal.
   • Include a pixi info so we know what type of system you are running on.
3. ❓ Ask the right questions, no question is wrong but there are badly formulated questions.
   • Add your specific use-case, e.g. you're in HPC, you're building a library, you're working on a slow internet machine, etc.
   • Tell us what you tried.
   • Add your workaround if you found any.
4. 🫂 Get others involved
   • Share your issue in our Discord or socials to drag attention to it.

[pavelzw]

Most upvoted issues: https://github.com/prefix-dev/pixi/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc