Thanks for your interest in contributing. Bug reports, feature ideas, and pull requests are all welcome.
Before opening an issue, please search existing issues to avoid duplicates. When filing a new one, use the bug report or feature request template and include the information it asks for.
For bug reports, the most useful details are:
- Your OS and Python version (
python --version) - The version of gitoverit you're running (
gitoverit --helpshows installed paths) - The exact command you ran and the output you got
- What you expected to happen instead
gitoverit uses uv for dependency management.
git clone https://github.com/mevanlc/gitoverit.git
cd gitoverit
uv syncInstall the CLI in editable mode so local changes are picked up:
uv tool install -e --force .The tasks/ directory contains lightweight scripts for common workflows:
uv run tasks/check # Pyright type checking
uv run tasks/test # unittest suiteBoth should pass before you open a pull request.
- Fork the repo and create a topic branch from
main. - Make focused changes — one logical change per PR keeps review fast.
- Add or update tests when you change behavior. Tests live in
tests/. - Run
uv run tasks/checkanduv run tasks/testlocally. - Update
README.mdif you change user-facing flags or output. - Open the PR using the template and link any related issues.
- Follow the structure documented in
AGENTS.md— particularly the split betweenreporting.py,progress.py, andoutput/. - Keep
RepoReportand worker arguments pickle-friendly (they cross process boundaries). - Prefer small, composable functions over large ones.
If you're unsure whether a change fits the project's scope, open an issue first to discuss before investing time in a PR.