How to contribute

Your contributions are essential for making the irc crate the best piece of software it could possibly be! We welcome contributions from programmers of all skill levels, and are happy to provide mentorship for new contributors working on bug fixes. To make the onboarding process as painless as possible for everyone, there are a few guidelines that we need contributors to follow.

Getting Started

Make sure you have a GitHub account.
Fork the repository on GitHub.

Making Changes

Create a topic branch from where you want to base your work.
- This is almost always the develop branch.
- Only target stable or a maintainer's feature branch if you are certain your fix must be on that branch.
- To quickly create a topic branch based on develop, run git checkout -b fix/develop/my_contribution develop. Please avoid working directly on the stable branch, and keep direct work on develop minor.
Make commits of logical and atomic units.
Check for unnecessary whitespace with git diff --check before committing.
Make sure you have added the necessary tests for your changes.
Run all the tests to assure nothing else was accidentally broken using cargo test. You can also run cargo test --no-default-features, but this is generally not relevant and will be handled by our continuous integration tools.
- Some tests related to configurations will fail if you don't run the mktestconfig.sh script.

Submitting Changes

Push your changes to a topic branch in your fork of the repository.
Submit a pull request to the aatxe/irc repository.
Await maintainer feedback and continuous integration results.
- We make an effort to triage quickly, but patience is appreciated!

Additional Resources

Code of Conduct
the irc crate docs
#rust-irc IRC channel on irc.mozilla.org

Credits

These contributing guidelines were inspired by the Puppet contributor guidelines.

2.1 KiB Raw Blame History