Thank you for contributing to Bazaar! Here are some instructions to get you started.
Welcome! We are glad that you are here! 💖
As you get started, you are in the best position to give us feedback on areas of our project that we need help with including:
- Problems found during setting up a new developer environment
- Documentation
- Bugs in our automation scripts and actions
If anything doesn't make sense, or doesn't work when you run it, please open a bug report and let us know!
We welcome many different types of contributions including:
- New features
- Builds, CI/CD
- Bug fixes
- Documentation
- Issue Triage
- Answering questions in Discussions
- Release management
- Translations - follow the dedicated instructions in that document
These are the issues that need the most amount of attention and would be an effective way to get started:
Sometimes there won’t be any issues with these labels. That’s ok! There is likely still something for you to work on. If you want to contribute but you don’t know where to start or can't find a suitable issue then feel free to post on the discussion forum
Once you see an issue that you'd like to work on, please post a comment saying that you want to work on it. Something like "I want to work on this" is fine.
The best way to reach us with a question when contributing is to ask on:
- The original github issue you want to contribute to
- The discussions area
GNOME Builder or
just build-flatpakSee Flatpak Docs
flatpak info io.github.kolunmi.BazaarG_MESSAGES_DEBUG=all flatpak run io.github.kolunmi.BazaarWhen you submit your pull request, or you push new commits to it, our automated systems will run some checks on your new code. We require that your pull request passes these checks, but we also have more criteria than just that before we can accept and merge it. We recommend that you check the following things locally before you submit your code:
- Use the GNU Style Guide
- Format your commits using
clang-format; see .clang-format - Follow the GNOME Commit Style