github-cheat-sheet/CONTRIBUTING.md

# Contributing

1. Fork the repository.
2. Add your section - make sure you follow the [styling](#styling) guide.
3. Commit changes.
4. Push your commit.
5. Create a Pull Request.

## Styling

- Use `###` headers for your sections.
- Also use `###` for categories (these should group together relevant sections) and `####` for subcategories.
- Add a link to your section/category to the contents section (use relative links).
- Make sure to include examples wherever possible (preferably GIFs).
- For command-line examples, wrap your commands in a `bash` code block. Ask [@rafalchmiel](https://github.com/rafalchmiel) or [@tiimgreen](https://github.com/tiimgreen) to take a screenshot (so that it is consistent with the rest) of the output if it has color, etc.
- At the end of your section, add a `Read more about...` link. This should directly link to [Git's](http://git-scm.com/docs) or [GitHub's](https://help.github.com/) documentation.
Add CONTRIBUTING.md, close #5 2014-04-13 12:26:24 +01:00			`# Contributing`

Improve contributing guide 2014-04-14 15:34:37 +01:00			`1. Fork the repository.`
			`2. Add your section - make sure you follow the [styling](#styling) guide.`
			`3. Commit changes.`
			`4. Push your commit.`
			`5. Create a Pull Request.`
Add CONTRIBUTING.md, close #5 2014-04-13 12:26:24 +01:00
			`## Styling`

Update contributing guide to fit new organization 2014-04-14 19:51:06 +01:00			- Use `###` headers for your sections.
			- Also use `###` for categories (these should group together relevant sections) and `####` for subcategories.
Improve contributing guide 2014-04-14 15:34:37 +01:00			`- Add a link to your section/category to the contents section (use relative links).`
			`- Make sure to include examples wherever possible (preferably GIFs).`
			- For command-line examples, wrap your commands in a `bash` code block. Ask [@rafalchmiel](https://github.com/rafalchmiel) or [@tiimgreen](https://github.com/tiimgreen) to take a screenshot (so that it is consistent with the rest) of the output if it has color, etc.
			- At the end of your section, add a `Read more about...` link. This should directly link to [Git's](http://git-scm.com/docs) or [GitHub's](https://help.github.com/) documentation.