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!
If you have something awesome to contribute to this list, this is how you do it.
If you have a GitHub account:
- Fork this repo.
- Make changes under correct section in
README.md - Update
Contents(if applicable) - Commit and open a Pull Request
If you don't have a GitHub account, make one!
- Access the Awesome MSP's GitHub page: https://github.com/guardzcom/awesome-msp
- Click on the
README.mdfile. - Now click on the edit icon.
- 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.
- Say why you're proposing the changes, and then click on "Propose file change".
- Submit the pull request!
Sometimes, a maintainer 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 contributing guidelines.
Here is a write up on how to change a Pull Request, and the different ways you can do that.