The pull request should have a useful title. Pull requests with Update readme.md as title will be closed right away because I'm so tired of nobody reading this document. Please carefully read everything in Adding to this list.
- Adding to this list
- Creating your own awesome list
- Adding something to an awesome list
- Updating your Pull Request
Please ensure your pull request adheres to the following guidelines:
- Search previous suggestions before making a new one, as yours may be a duplicate.
- Make sure the list is useful before submitting. That implies it has enough content and every item has a good succinct description. It also should have good documentation of the messaging API to interact with it.
- Make an individual pull request for each suggestion.
- Use the following format:
### [Extension name](api docs link)`
<short description what the extension provides to other extensions>.
#### Supports
- [Browser name](language independent store/download link)- Additions should be added to the bottom of the relevant category.
- New categories or improvements to the existing categorization are welcome.
- 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!
To create your own list, check out the instructions.
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 is a write up on how to change a Pull Request, and the different ways you can do that.