Thank you for considering contributing to MSSQLand! Your efforts help make this tool better for everyone, and every contribution is valued. This document outlines the guidelines for contributing to ensure a productive and fair collaboration.
- Fork the Repository: Use the GitHub "Fork" button to create your own copy of the repository.
- Create a Branch: Use a descriptive branch name is needed
git checkout -b feature/add-new-feature- Test Your Changes: Verify that your changes work as intended and don’t introduce issues.
- Submit a Pull Request: Push your branch and create a PR with a clear description of your changes and their purpose.
To ensure accountability and transparency in contributions, always sign your commits. This helps verify the authenticity of the commit and ensures a clear history of who contributed what.
Follow GitHub’s guide on signing commits to generate a GPG key and configure it for Git.
Signed commits ensure the integrity and authenticity of contributions, reflecting the highest standards of professionalism in the project.
Contributions are preserved transparently in Git history. No fear to have here—no one will copy-paste your code without adhering to the collaborative ethos of open-source.
If the code needs changes, it will be merged - yet accepted - into a specific branch to preserve the contributor's effort while allowing for refactoring and thorough review.
- All commits will be retained in the repository, ensuring proper credit is given.
- Any modifications or refactors will be performed after merging, with clear documentation of changes.
- Feedback will be provided with reasons for rejection.
- You are encouraged to resubmit after addressing the concerns.
- No one’s contributions will be erased or dismissed without acknowledgment.