Contributing Guidelines

Image of Kevin R. Barnes

Oftentimes open source projects place a CONTRIBUTING file in the root directory. It explains how a participant should do things like format code, test fixes, and submit patches. Here is a fine example from puppet and another one from factory_girl_rails. From a maintainer’s point of view, the document succinctly communicates how best to collaborate. And for a contributor, one quick check of this file verifies their submission follows the maintainer’s guidelines.

Contributors Wanted: Inquire Within

Today we added support for sharing your preferred policy for contributions with the folks wanting to collaborate with you on your project.

We’ve tried making this easy for everyone. As a maintainer, all you have to do is add a CONTRIBUTING file (or if you’re using Markdown) to the root of your repository. Then we will add a link to your file when a contributor creates an Issue or opens a Pull Request.

Now, as soon as your collaborators start participating, they can easily find the guidelines you’d like them to follow.

If you don’t see a CONTRIBUTING file in your favorite project, open a pull request and add one.

Join us at GitHub Universe

Our largest product and community conference is returning to the Palace of Fine Arts in San Francisco, November 13-14. Hear what's next for the GitHub platform, find inspiration for your next project, and connect with developers who are changing the world.

Get tickets

GitHub Actions now supports CI/CD

GitHub Actions makes it easier to automate how you build, test, and deploy your projects on any platform, including Linux, macOS, and Windows. Try out the beta before GitHub Actions is generally available on November 13.

Sign up for the beta