First off, thank you for considering contributing to CryptoGuard. It's people like you that make CryptoGuard such a great tool.
By participating in this project, you are expected to uphold our Code of Conduct.
This section guides you through submitting a bug report for CryptoGuard. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
- Use a clear and descriptive title for the issue to identify the problem.
- Describe the exact steps which reproduce the problem in as many details as possible.
- Provide specific examples to demonstrate the steps.
This section guides you through submitting an enhancement suggestion for CryptoGuard, including completely new features and minor improvements to existing functionality.
- Use a clear and descriptive title for the issue to identify the suggestion.
- Provide a step-by-step description of the suggested enhancement in as many details as possible.
- Provide specific examples to demonstrate the steps.
- Fill in the required template.
- Do not include issue numbers in the PR title.
- Include screenshots and animated GIFs in your pull request whenever possible.
- Follow the Python style guides.
- End all files with a newline.
- Use the present tense ("Add feature" not "Added feature").
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...").
- Limit the first line to 72 characters or less.
- Reference issues and pull requests liberally after the first line.
All Python must adhere to PEP 8.
This section lists the labels we use to help us track and manage issues and pull requests.
bug
- Issues that are bugs.enhancement
- Issues that are feature requests.documentation
- Issues or pull requests related to documentation.good first issue
- Good for newcomers.
Your contributions to open source, large or small, make great projects like this possible. Thank you for taking the time to contribute.