Thanks for your interest in contributing to chdscript! 🎉
-
Fork the repo and create your feature branch:
git checkout -b feature/my-new-feature
-
Commit your changes with clear messages:
git commit -m "Add support for XYZ" -
Push to the branch:
git push origin feature/my-new-feature
-
Open a Pull Request against
main.
- Follow the existing coding style (Bash best practices:
set -euo pipefail, quoting variables, etc.). - Use inline comments when adding non-obvious logic.
- Keep logging consistent (
logvs.verify_output_log).
- Test against a directory with both single-disc and multi-disc games.
- Run at least once with:
--recursive--keep-originals
- Confirm space savings and CHD verification messages.
We use Semantic Versioning (semver).
Bump version numbers when you:
MAJOR: Break backward compatibilityMINOR: Add new functionality in a backward-compatible mannerPATCH: Fix bugs or make small improvements
💡 If unsure, open an Issue first to discuss before coding.