8000 CONTRIBUTING.md · sureshg/github-cheat-sheet@704d07f · GitHub
[go: up one dir, main page]

Skip to content

Commit 704d07f

Browse files
committed
CONTRIBUTING.md
1 parent 3b04f63 commit 704d07f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

CONTRIBUTING.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Contributing
22

33
1. Fork the repository.
4-
2. Add your section - make sure you follow the [styling](#styling) guide.
4+
2. Add your section - make sure you follow the styling guide below.
55
3. Commit changes.
66
4. Push your commit.
77
5. Create a Pull Request.
@@ -12,6 +12,6 @@
1212
- Also use `###` for categories (these should group together relevant sections) and `####` for subcategories.
1313
- Add a link to your section/category to the contents section (use relative links).
1414
- Make sure to include examples wherever possible (preferably GIFs).
15-
- 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.
16-
- 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.
15+
- For command-line examples, wrap your commands in a `bash` code block.
16+
- At the end of your section, add a `Read more about...` link. This should directly link to [Git's](http://git-scm.com/docs), [GitHub's](https://help.github.com), or the relevant documentation.
1717
- If your contribution is a translation, add a (relative) link to the README above the [Table of Contents](README.md#table-of-contents).

0 commit comments

Comments
 (0)
0