Skip to content

Latest commit

 

History

History
51 lines (30 loc) · 2.59 KB

CONTRIBUTING.md

File metadata and controls

51 lines (30 loc) · 2.59 KB
Raw

Contributing to DevSecTricks

First off, thank you for considering contributing to DevSecTricks! We appreciate your effort and enthusiasm in making the internet a safer place for developers and users alike.

DevSecTricks focuses on developer security topics, tools, and other resources. This repository serves as a hub for all things security in the development realm.

How Can I Contribute?

Reporting Bugs

  • Ensure the bug was not already reported by searching on GitHub under Issues.
  • If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.

Suggesting Enhancements

  • Before creating enhancement suggestions, please check if there's already a suggestion which matches your own.
  • When you are creating a new enhancement suggestion, include as many details as possible, including the steps that you imagine you would take if the feature you're requesting existed.

Pull Requests

  1. Fork the repo.
  2. Create your feature branch: git checkout -b my-new-feature.
  3. Commit your changes: git commit -am 'Add some feature'.
  4. Push to the branch: git push origin my-new-feature.
  5. Submit a pull request.

Sharing Resources or Tools

If you've stumbled upon some great developer security resources or tools that you believe would benefit the community:

  1. Ensure that no one else has already submitted the same resource.
  2. Clearly state the resource's purpose and its relevance to developer security.
  3. Always reference content from other pages accurately. Ensure that you have the rights or permission to share any material, and always give credit where credit is due.

Updating Documentation

Documentation is vital! If you notice missing or erroneous documentation, please submit a pull request with your suggested changes.

Conduct

We have a code of conduct; by participating in this project, you agree to abide by its terms.

Recognition

We recognize all our contributors and appreciate the time and energy they put into the project. Thank you for your efforts and for making a positive impact on developer security!

Remember, contributions don't necessarily have to be large or complicated. Even the smallest changes can make a big difference! We appreciate all forms of contributions, from bug fixes to new resources.

Happy developing and stay secure!