awesome-actions/contributing.md

# Contribution Guidelines

Please note that this project is released with a [Contributor Code of Conduct](code-of-conduct.md). By participating in this project you agree to abide by its terms.

> The pull request should have a useful title. Pull requests with `Update readme.md` as title will be closed. Please carefully read everything in `Adding to this list`.

## Table of Contents

- [Adding to this list](#adding-to-this-list)
- [Creating your own awesome list](#creating-your-own-awesome-list)
- [Adding something to an awesome list](#adding-something-to-an-awesome-list)
- [Updating your Pull Request](#updating-your-pull-request)

## Adding to this list

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 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.
- Use Title Casing.
- Use the following format: `[List Name](link)`
- Link additions should be added to the bottom of the relevant category.
- New categories or improvements to the existing categorization are welcome.
- Please check your spelling and grammar.
- Make sure your text editor is set to remove trailing whitespace.
- The pull request and commit should have a useful title.
- The body of your commit message should contain a link to the repository.

Thank you for your suggestions!

## Adding something to an awesome list

If you have something awesome to contribute to an awesome list, this is how you do it.

You'll need a [GitHub account](https://github.com/join)!

1. Access the awesome list's GitHub page. For example: https://github.com/sdras/awesome-actions
2. Click on the `readme.md` file: ![Step 2 Click on Readme.md](https://cloud.githubusercontent.com/assets/170270/9402920/53a7e3ea-480c-11e5-9d81-aecf64be55eb.png)
3. Now click on the edit icon. ![Step 3 - Click on Edit](https://cloud.githubusercontent.com/assets/170270/9402927/6506af22-480c-11e5-8c18-7ea823530099.png)
4. You can start editing the text of the file in the in-browser editor. Make sure you follow guidelines above. You can use [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). ![Step 4 - Edit the file](https://cloud.githubusercontent.com/assets/170270/9402932/7301c3a0-480c-11e5-81f5-7e343b71674f.png)
5. Say why you're proposing the changes, and then click on "Propose file change". ![Step 5 - Propose Changes](https://cloud.githubusercontent.com/assets/170270/9402937/7dd0652a-480c-11e5-9138-bd14244593d5.png)
6. Submit the [pull request](https://help.github.com/articles/using-pull-requests/)!

## Updating your Pull Request

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.
initial commit 2018-10-20 21:08:16 -04:00			`# Contribution Guidelines`

			`Please note that this project is released with a [Contributor Code of Conduct](code-of-conduct.md). By participating in this project you agree to abide by its terms.`

update contributing- remove broken link and clarify requests 2018-10-21 16:12:41 -04:00			> The pull request should have a useful title. Pull requests with `Update readme.md` as title will be closed. Please carefully read everything in `Adding to this list`.
initial commit 2018-10-20 21:08:16 -04:00
			`## Table of Contents`

			`- [Adding to this list](#adding-to-this-list)`
			`- [Creating your own awesome list](#creating-your-own-awesome-list)`
			`- [Adding something to an awesome list](#adding-something-to-an-awesome-list)`
			`- [Updating your Pull Request](#updating-your-pull-request)`

			`## Adding to this list`

			`Please ensure your pull request adheres to the following guidelines:`

			`- Search previous suggestions before making a new one, as yours may be a duplicate.`
Mention the different sections in contributing now 2019-02-10 14:01:57 -05:00			`- 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.`
update contributing- remove broken link and clarify requests 2018-10-21 16:12:41 -04:00			`- Please don't use bold or italics unless it's somehow appropriate to the link.`
initial commit 2018-10-20 21:08:16 -04:00			`- 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.`
update contributing- remove broken link and clarify requests 2018-10-21 16:12:41 -04:00			`- Use Title Casing.`
initial commit 2018-10-20 21:08:16 -04:00			- Use the following format: `[List Name](link)`
			`- Link additions should be added to the bottom of the relevant category.`
			`- New categories or improvements to the existing categorization are welcome.`
Fix typo 2018-10-23 01:23:42 -04:00			`- Please check your spelling and grammar.`
initial commit 2018-10-20 21:08:16 -04:00			`- Make sure your text editor is set to remove trailing whitespace.`
			`- The pull request and commit should have a useful title.`
			`- The body of your commit message should contain a link to the repository.`

			`Thank you for your suggestions!`

			`## Adding something to an awesome list`

			`If you have something awesome to contribute to an awesome list, this is how you do it.`

			`You'll need a [GitHub account](https://github.com/join)!`

update contributing- remove broken link and clarify requests 2018-10-21 16:12:41 -04:00			`1. Access the awesome list's GitHub page. For example: https://github.com/sdras/awesome-actions`
initial commit 2018-10-20 21:08:16 -04:00			2. Click on the `readme.md` file: ![Step 2 Click on Readme.md](https://cloud.githubusercontent.com/assets/170270/9402920/53a7e3ea-480c-11e5-9d81-aecf64be55eb.png)
			`3. Now click on the edit icon. ![Step 3 - Click on Edit](https://cloud.githubusercontent.com/assets/170270/9402927/6506af22-480c-11e5-8c18-7ea823530099.png)`
			`4. You can start editing the text of the file in the in-browser editor. Make sure you follow guidelines above. You can use [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). ![Step 4 - Edit the file](https://cloud.githubusercontent.com/assets/170270/9402932/7301c3a0-480c-11e5-81f5-7e343b71674f.png)`
			`5. Say why you're proposing the changes, and then click on "Propose file change". ![Step 5 - Propose Changes](https://cloud.githubusercontent.com/assets/170270/9402937/7dd0652a-480c-11e5-9138-bd14244593d5.png)`
			`6. Submit the [pull request](https://help.github.com/articles/using-pull-requests/)!`

			`## Updating your Pull Request`

			`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.`

Mention the different sections in contributing now 2019-02-10 14:01:57 -05:00			`[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.`