Please note that this project is released with a Contributor Code of Conduct. By participating in this project, you agree to abide by its terms.
Please ensure your pull request adheres to the following guidelines:
- Search previous suggestions to make sure your suggestion isn't a duplicate.
- Make sure each list item is useful before adding it.
- Create individual pull requests/issues for each suggestion.
- Use title-casing (AP style) in the following format:
* [List Name](link)
- Link additions should be added in alphabetical order in the relevant category.
- New categories or changes 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.
- Annotate your PR to clarify what you did if the diff is confusing.
Thank you for your suggestions!
Either make an issue with the template Add Application, which will then automatically create a pull request, or make your manual changes as follows:
If you don't have a GitHub account, make one!
- Fork this repo.
- Make changes under correct section in
README.md
- Update
Contents
(if applicable) - Commit and open a 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-windows list guidelines.
Here is a write up on how to change a Pull Request, and the different ways you can do that.