Skip to content

Latest commit

 

History

History
35 lines (24 loc) · 2.04 KB

CONTRIBUTING.md

File metadata and controls

35 lines (24 loc) · 2.04 KB
Raw

Contribution Guidelines

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. These guidlines were inspired by Awesome.

Adhering to guidelines while 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.
  • 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 the following format: - [ ] your text here
  • 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.

Adding something to this list

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

You'll need a GitHub account!

  1. Access this list's GitHub page here: https://github.com/virajkulkarni14/WebDeveloperSecurityChecklist
  2. Click on the CHECKLIST.md file.
  3. Now click on the edit icon.
  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.
  5. Say why you're proposing the changes, and then click on "Propose file change".
  6. Submit the pull request!

Updating your Pull Request

Sometimes, a maintainer of this 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 above guidelines.

Here is a write up on how to change a Pull Request, and the different ways you can do that.