Thanks for contributing to gitdropbox.
- Fork and clone the repository.
- Ensure Git and Bash are available.
- Create a working branch:
git checkout -b your-branch-name
Run these before opening a pull request:
bash -n gitdropbox
shellcheck gitdropbox tests/smoke.sh
bash tests/smoke.shIf shellcheck is not installed locally, CI will still run it.
- Keep the script POSIX-aware where practical, but Bash-first and explicit.
- Preserve strict mode in scripts:
set -euo pipefail. - Prefer defensive checks and actionable error messages.
- Keep docs in sync when adding/changing CLI options.
- Use LF line endings (
.gitattributesenforces this in Git).
- Describe the problem and why your change is needed.
- Keep changes focused and minimal.
- Include test updates when behavior changes.
- Update README.md and doc/CHANGELOG.md when user-facing behavior changes.
Maintainers should follow doc/RELEASE_CHECKLIST.md before publishing.