PyGitTools
Hooks, tooling, and pygit2 workflows used by PyGitWeb. Can be used headless for many purposes.
PGT
pgt is a terminal UI for commits, branches, tasks, and worktrees. The home page has Status, Log, Tasks, and Worktrees tabs. H / L switch tabs, J / K move the selection, Q or Ctrl-C quits, and ? opens help. On Status, ! or the Actions row runs project scripts from pyproject.toml or actions.toml. Full key bindings are in the in-app help (src/pygittools/help.md).
To run from the repo root, use uv run pgt.
Task objects may include points, a Fibonacci story-point value: 0, 1, 2, 3, 5, 8, 13, or 21. Leave it unset when the task is unestimated.
Hook framework
pygittools.hooks provides a thin Hook base class plus one subclass per git hook type
(client- and server-side). Receive-pack hooks (PreReceive, PostReceive) parse their
ref-update lines via parse_ref_updates(stdin).
pygittools.hooks_notify adds PreReceiveNotify / PostReceiveNotify: minimal hook
variants that POST ?project=<name> to a pygitweb /_internal/notify endpoint so its
long-poll updates=true subscribers wake up immediately on each push. Notification
failures never reject the push.
See hook_samples/ for ready-to-use scripts.
MCP task server
Boards, tasks, and comments stored in Git can be exposed to AI tools via MCP.
Configure the repository path with PYGITTOOLS_REPO, or set PYGITWEB_PROJECTROOT and pass a
project argument to each tool. When neither is set, the server discovers a repo from the current
working directory.
Run locally:
PYGITTOOLS_REPO=/path/to/repo uv run pygittools-mcp
Cursor project config (.cursor/mcp.json):
{
"mcpServers": {
"pygittools-tasks": {
"command": "uv",
"args": ["run", "--directory", "/path/to/pygitweb", "pygittools-mcp"],
"env": {
"PYGITTOOLS_REPO": "/path/to/your/repo"
}
}
}
}
Tools: list_boards_tool, list_tasks_tool, get_task_tool, board_by_status_tool.
Resources: board://{board_name}, task://{task_ref}.
Metadata
Release files for pygittools 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pygittools-0.3.1.tar.gz | 76.3 kB | Without provenance | Details for pygittools-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pygittools-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for pygittools-0.3.1-py3-none-any.whl |
Total release size: 187.4 kB
Release files / pygittools-0.3.1.tar.gz
| Download URL | pygittools-0.3.1.tar.gz |
|---|---|
| Size | 76.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a33e4eb3bdb2cdae25cd6913ffcc270c053fc06484173203dcc6ee58c8901e0c
|
|
BLAKE2b-256 checksum How to use checksums |
696a63e03237c6e06ef51b60a72b17b1417b473e3a7bef8a2c5fbb1477f2082d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.23 {"installer":{"name":"uv","version":"0.11.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / pygittools-0.3.1-py3-none-any.whl
| Download URL | pygittools-0.3.1-py3-none-any.whl |
|---|---|
| Size | 111.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a0bf0b11688847f1a309a710a5fac0a14f2c6964393cf9e200c277f27af1cdb
|
|
BLAKE2b-256 checksum How to use checksums |
16f063d7d85f41c032992c3e4f9c894d21da2d83b7b317e3a8f08849e8114d15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.23 {"installer":{"name":"uv","version":"0.11.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for pygittools 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.