-
Notifications
You must be signed in to change notification settings - Fork 167
Home
Bruce edited this page May 8, 2022
·
6 revisions
Welcome to the Cyber-Security-University wiki contribution guide!
Your pull request should have a useful title. Please carefully read everything in Adding to this list. Make sure it is also accessible without any paywall that focuses on learn by doing type of style.
- Adding to this list
- Creating your own awesome list
- Adding something to an awesome list
- Updating your Pull Request
β 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 item you are adding is useful (and, you know, awesome) before submitting.
- Make an individual pull request for each suggestion.
- Use title-casing (AP style).
- Use the following format:
[Item Name](link)
- 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!
β Adding something to an awesome list
If you have something awesome to contribute to an awesome list, this is how you do it.
You'll need a GitHub account!
- Access the awesome list's GitHub page. For example: https://github.com/sindresorhus/awesome
- Click on the
readme.md
file: - 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!
β 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 awesome-* list guidelines.