Skip to content

Latest commit

 

History

History
34 lines (22 loc) · 1.88 KB

contributing.md

File metadata and controls

34 lines (22 loc) · 1.88 KB

Contribution Guidelines

Please ensure your pull request adheres to the following:

  • Search previous suggestions before making a new one to ensure yours is not a duplicate.
  • Make an individual pull request for each suggestion.
  • Use the following format: [NAME](LINK) Badges - DESCRIPTION.
  • New categories, or improvements to the existing ones are welcome.
  • End all descriptions with a period.
  • Try to ensure your pull requests only have one commit if possible. You can squash your commits into one before submitting.
  • Make your pull request titles and descriptions as detailed as possible. Explain why an asset or resources deserves to be added to the list.
  • Make sure your additions are in alphabetical order. This includes the headers and items themselves.
  • Ensure that assets you submit are of high quality, documented well, and are recently maintained. It also helps if they're popular so I can research them before adding them to the list.
  • This is not meant to be used as a list to advertise your own assets. Free or open-source assets should be prioritized over paid assets if they are of similar quality and feature sets.

Thanks!

Badge Templates

Coppy the following URLs and replace {username} with the correct GitHub username and {repo} with the repository you are submitting.

GH issue badge

[![GitHub issues](https://img.shields.io/github/issues/{username}/{repo}?style=flat-square)](https://github.com/{username}/{repo})

GH stars badge

[![GitHub stars](https://img.shields.io/github/stars/{username}/{repo}?style=flat-square)](https://github.com/{username}/{repo}/stargazers)

GH last commit badge

![last commit](https://img.shields.io/github/last-commit/{username}/{repo}?style=flat-square)

Working on your first Pull Request? You can learn how from this free series How to Contribute to an Open Source Project on GitHub