Anchor4Git
A highly-minimal workflow tool for small teams (2–4 people) using Git. Anchor4Git wraps Git into a simple Download → Edit → Upload mental model so users never need to know Git commands.
Features
- No Git knowledge required — users never run Git commands directly.
- Workspace-first — users edit files normally, anchor4git handles versioning.
- Auto-save before risky operations — dirty workspaces are saved automatically.
- Force push model — simplified for small, trusted teams.
- Conflicts handled in editor — visual merge UX instead of CLI confusion.
Installation
For non-contributors:
pipx anchor4git
For contributors:
git clone https://github.com/invoke-zero/anchor4git.git
cd anchor4git
pip install -r requirements.txt
python -m build
Usage
ag fetch - Download latest work from the remote
ag save - Save a snapshot of your workspace
ag upload - Publish your work to the remote
ag info - View project dashboard and history
ag goto - Navigate to a previous save
ag config - Open project configuration
All commands have short aliases (f, s, u, i, g, c).
Contributing
Contributions are welcome! Here's how you can help:
- Fork the repository.
- Create a feature branch:
git checkout -b feature-name
- Commit your changes:
git commit -m "Add new feature"
- Push your branch:
git push origin feature-name
- Submit a pull request.
Please read the CONTRIBUTING.md for detailed guidelines.
License
This project is licensed under the Invoke0 Standard License 1.0 (I0SL-1.0) License - see the LICENSE file for details.
Acknowledgements
Metadata
Release files for anchor4git 0.1.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 |
|---|---|---|---|---|
| anchor4git-0.1.1.tar.gz | 13.0 kB | Without provenance | Details for anchor4git-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| anchor4git-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for anchor4git-0.1.1-py3-none-any.whl |
Total release size: 31.0 kB
Release files / anchor4git-0.1.1.tar.gz
| Download URL | anchor4git-0.1.1.tar.gz |
|---|---|
| Size | 13.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c71a16ade48b563b11067aa513d201fca30851418ae7291b4715bdbde3a395c
|
|
BLAKE2b-256 checksum How to use checksums |
579d14b53490b17fc47d52796604858270a9a883809ec294c70a6079712165a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.17 {"installer":{"name":"uv","version":"0.9.17","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 / anchor4git-0.1.1-py3-none-any.whl
| Download URL | anchor4git-0.1.1-py3-none-any.whl |
|---|---|
| Size | 18.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
824fbd9eb9bee08822f7832435163e5893d4108e7455fb276cdf2b8f4d13c674
|
|
BLAKE2b-256 checksum How to use checksums |
01db70d648982a52fcd550a070f7948555f89a283010f29900610691e03f7bde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.17 {"installer":{"name":"uv","version":"0.9.17","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 anchor4git 0.1.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.