First off, thank you for considering contributing to our project! It's people like you who make it a reality for users to benefit from the amazing features our application offers.
Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.
This section guides you through submitting a bug report for our project. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
- 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.
This section guides you through submitting an enhancement suggestion for our project, including completely new features and minor improvements to existing functionality.
- Ensure the enhancement was not already suggested by searching on GitHub under Pull Requests.
- If you find a suggestion that is not yet implemented and you would like to see, feel free to give it a thumbs up or add your comments.
- If you're unable to find an open issue addressing the enhancement, open a new one. Be sure to include a title and clear description, and as much detail as possible.
The process described here has several goals:
- Maintain quality of the codebase.
- Fix problems that are important to users.
- Engage the community in working towards the best possible solutions.
Please follow these steps to have your contribution considered by the maintainers:
- Fork the repository and create your branch from
main. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
- 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.
- When only changing documentation, include
[ci skip]in the commit description.
- Follow the code style conventions that are used in the project.
- Ensure that your code passes ESLint checks.
This project and everyone participating in it is governed by the Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to piyushvrm072001@gmail.com.
Thank you for considering contributing to the Encryption and Decryption with JavaScript project!