Thank you for considering contributing to this project! By following the steps below, we can ensure a smooth and secure collaboration.
To get started, fork this repository by clicking the "Fork" button at the top of the repository page.
Create a new branch for your feature or bug fix. Use descriptive branch names like feature/add-new-feature
or fix/bug-name
.
git checkout -b feature/your-feature-name
Make your changes, test them thoroughly, and ensure everything works as expected.
Ensure your commits are signed (optional, but recommended for security):
git commit -S -m "Add new feature"
Push your branch to your forked repository:
git push origin feature/your-feature-name
Open a pull request (PR) to the main
branch of this repository. Please ensure the following:
- The code is clean and follows project guidelines.
- Any tests, if applicable, have been updated or added.
- The pull request is focused on a single feature or bug fix.
Our team will review the pull request, and feedback will be provided if any changes are necessary. All pull requests require approval before being merged into the main
branch.
For security purposes, the main
branch is protected. The following rules are enforced:
- All contributions must go through a pull request and require at least one approval.
- Direct pushes to the
main
branch are not allowed.
We take security seriously. To ensure contributions do not introduce vulnerabilities or malicious payloads, please follow these security guidelines:
- Code Scanning: All pull requests will be automatically scanned for security vulnerabilities using tools like CodeQL.
- Signed Commits: To verify the identity of contributors, we recommend signing your commits using Git’s GPG signing feature.
- Review Process: Every pull request will be manually reviewed by maintainers before merging.
- No Binary Files: Do not upload binary files (e.g.,
.exe
,.dll
) or any precompiled code. This helps prevent potential security risks. - Respect
.gitignore
: Ensure sensitive files like environment variables or credentials (e.g.,.env
files) are not committed. - Dependabot Alerts: Vulnerabilities in dependencies will be automatically flagged and addressed before merging.
If you discover any security vulnerabilities in the project, please report them privately by emailing [[email protected]]. Do not publicly disclose vulnerabilities until we have had the chance to investigate and address them.
Please note that all contributors are expected to follow our Code of Conduct to maintain a respectful and productive community.
Thank you for contributing! Your help in improving this project is greatly appreciated. If you find this project helpful, please consider ⭐️ starring it on GitHub to help others discover it.
Happy coding! 🎉