1.6 KiB
Contributing
👍🎉 First off, thanks for taking the time to contribute! 🎉👍
The following is a set of guidelines for contributing to the Jenkins Operator. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
In this project we appreciate any kind of contributions: code, documentation, design, etc. Any contribution counts, and the size does not matter!
Newcomers
If you are a newcomer contributor and have any questions, please do not hesitate to ask in the #jenkins-operator Slack Channel.
Table Of Contents
Code of Conduct
This project and everyone participating in it is governed by the Atom Code of Conduct. By participating, you are expected to uphold this code.
Commit Messages
All commit messages should follow these best practices, specifically:
- Start with a subject line
- Contain a body that explains why you're making the change you're making
- Reference an issue number one exists, closing it if applicable (with text such as "Fixes #245" or "Closes #111")
Not sure what to put? Try to Include:
- What is the problem being solved?
- Why is this the best approach?
- What other approaches did you consider?
- What side effects will this approach have?
- What future work remains to be done?