Pull Requests

Thank you for taking interest in contributing to one of Method Security's open source cybersecurity tools!

1. Every Pull Request should have an associated bug or feature issue unless you are fixing a trivial documentation issue.
2. Please add the associated Issue link in the PR description.
3. Your PR is more likely to be accepted if it focuses on just one change.
4. There's no need to add or tag reviewers.
5. If a reviewer commented on your code or asked for changes, please remember to respond with comment. Do not mark discussion as resolved. It's up to reviewer to mark it resolved (in case if suggested fix addresses problem properly). PRs with unresolved issues should not be merged (even if the comment is unclear or requires no action from your side).
6. Please include a comment with the results before and after your change.
7. Your PR is more likely to be accepted if it includes tests (We have not historically been very strict about tests, but we would like to improve this!).
8. If your PR affects the user experience in some way, please update the README.md and the CLI help accordingly.