From f6f52764ee25f4fef4dcbc75c75946c44c75762b Mon Sep 17 00:00:00 2001 From: Sarah Drasner Date: Sun, 10 Feb 2019 09:01:57 -1000 Subject: [PATCH] Mention the different sections in contributing now --- contributing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contributing.md b/contributing.md index 0d2c886..1a62b5a 100644 --- a/contributing.md +++ b/contributing.md @@ -16,7 +16,7 @@ Please note that this project is released with a [Contributor Code of Conduct](c Please ensure your pull request adheres to the following guidelines: - Search previous suggestions before making a new one, as yours may be a duplicate. -- Please put your new addition at the end of the list. +- Please put your new addition at the end of the list of whatever section it is most relevant to. If you don't find a section that it belongs in, please make one. - Please don't use bold or italics unless it's somehow appropriate to the link. - Make sure the list is useful before submitting. That implies it has enough content and every item has a good succinct description. - Make an individual pull request for each suggestion. @@ -48,4 +48,4 @@ You'll need a [GitHub account](https://github.com/join)! Sometimes, a maintainer of an awesome list will ask you to edit your Pull Request before it is included. This is normally due to spelling errors or because your PR didn't match the awesome-\* list guidelines. -[Here](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) is a write up on how to change a Pull Request, and the different ways you can do that. \ No newline at end of file +[Here](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) is a write up on how to change a Pull Request, and the different ways you can do that.