Skip to content

Latest commit

 

History

History
31 lines (16 loc) · 1.39 KB

CONTRIBUTING.md

File metadata and controls

31 lines (16 loc) · 1.39 KB

Contributing to AWS Attacks Monitoring Project

We welcome contributions to the AWS Attacks Monitoring Project! If you have something to add or improve, please follow these guidelines to contribute.

How to Contribute

  1. Fork the Repository: Start by forking the repository and then cloning it locally on your machine.

  2. Create a New Branch: Create a new branch for your contributions. It's best to name the branch something descriptive.

  3. Make Your Changes: Add new IOCs, update analysis, or improve documentation. Make sure your changes are well-documented and clear.

  4. Commit Your Changes: Write clear, concise commit messages that explain your changes.

  5. Push to Your Fork: Push your changes to your forked repository.

  6. Submit a Pull Request: Open a pull request to the main repository. Provide a clear description of what your changes are and why they are necessary.

Pull Request Review

Once your pull request is submitted, it will be reviewed by the maintainers. They may suggest changes or improvements to your submission.

Code of Conduct

By contributing, you agree to abide by the principles and guidelines set out in the Code of Conduct.

Questions or Issues?

If you have any questions or run into any issues, please open an issue in the repository, and we'll be happy to help.

Thank you for your contributions and for helping to improve cloud security!