GTO
Git Tag Ops. Turn your Git repository into an Artifact Registry:
- Registry: Track new artifacts and their versions for releases and significant changes.
- Lifecycle Management: Create actionable stages for versions marking status of artifact or it's readiness to be consumed by a specific environment.
- GitOps: Signal CI/CD automation or other downstream systems to act upon these new versions and lifecycle updates.
GTO works by creating annotated Git tags in a standard format.
💡 Together with DVC, GTO serves as a backbone for Git-based Iterative Studio Model Registry.
Installation
GTO requires Python 3. It works on any OS.
$ pip install gto
This will install the gto
command-line interface (CLI) and
make the Python API available for use in code.
Getting started
To Get Started, please head to GTO docs.
Contributing
Contributions are welcome! Please see our Contributing Guide for more details.
Check out the DVC weekly board to learn about what we do, and about the exciting new functionality that is going to be added soon.
Thanks to all our contributors!
How to setup GTO development environment
- Clone this repository
$ git clone git@github.com:iterative/gto.git
$ cd gto
- Create virtual environment named
venv
$ python3 -m venv .venv
$ source .venv/bin/activate
Install python libraries
$ pip install --upgrade pip ".[tests]"
- Run
$ pytest --basetemp=pytest-basetemp
This will create pytest-basetemp/ directory with some fixtures that can serve
as examples.
Notably, check out this dir:
$ cd pytest-basetemp/test_api0/
$ gto show -v
The code that generates this folder could be found in this fixture.
To continue experimenting, call gto --help
Copyright
This project is distributed under the Apache license version 2.0 (see the LICENSE file in the project root).
By submitting a pull request to this project, you agree to license your contribution under the Apache license version 2.0 to this project.
2 maintainers
Release files for gto 1.10.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 | |
|---|---|---|---|
| gto-1.10.1.tar.gz | 60.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gto-1.10.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size:105.7 kB
Release files / gto-1.10.1.tar.gz
| Download URL | gto-1.10.1.tar.gz |
|---|---|
| Size | 60.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2a008650e7be42b7e3dd65e2eef360d466553e3b41d8f37dae38328d84fd224
|
|
BLAKE2b-256 checksum How to use checksums |
669ccf74e391f76ff2afd7aee9bdd0f1b191c0522ba8190439bfa3b2672f222a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 9, 2026.
Transparency logRelease files / gto-1.10.1-py3-none-any.whl
| Download URL | gto-1.10.1-py3-none-any.whl |
|---|---|
| Size | 45.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f357f7dee2cf91552408545e17f53a4ea54d0d16e676e35b92edf1291414d06d
|
|
BLAKE2b-256 checksum How to use checksums |
88af23fba84f3e03fcf58bd73e1d28ef9db7b46c5b48df95fae4b5f658db7993
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 9, 2026.
Transparency log
