To help your project contributors do good work, you can add a file with contribution guidelines to the root of your project's repository. Then, whenever someone opens a pull request or creates an issue, they will see a link to that file.
For the repository owner, contribution guidelines are a way to quickly communicate how people should contribute.
For contributors, these guidelines help them verify that they're submitting well-formed pull requests and opening useful issues.
For both owners and contributors, contribution guidelines save time and hassle generated by improperly created pull requests or issues that have to be rejected and re-submitted.
Adding a CONTRIBUTING file
On GitHub Enterprise, navigate to the main page of the repository.
Above the file list, click New file.
In the file name field, type CONTRIBUTING or CONTRIBUTING.md (with all caps!). Adding the
.mdextension will create a Markdown file.
In the new file, add contribution guidelines. These could include:
- Steps for creating good issues or pull requests.
- Links to external documentation, mailing lists, or a code of conduct.
- Community and behavioral expectations.
At the bottom of the page, type a short, meaningful commit message that describes the change you made to the file.
Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is
master, you should choose to create a new branch for your commit and then create a pull request.
Click Propose new file.
Examples of contribution guidelines
If you're stumped, here are some good examples of contribution guidelines:
- The Atom editor contribution guidelines.
- The Ruby on Rails contribution guidelines.
- The Open Government contribution guidelines.
- The Open Source Guides' section "Starting an Open Source Project"