git-system-follower
git-system-follower (gsf) is a package manager for Git providers.
👀 Overview • 🔧 Problems It Solves • 🌟 Key Features • 🎯 Key Beneficiaries • 📦 Install • 📃 Docs
Supported resources
Git providers
👀 Overview
gsf designed to streamline the management of repository branch content and configuration. By automating installations, updates, and removals, gsf reduces manual intervention, prevents errors, and ensures a consistent state across projects.
If you’re managing CI/CD pipelines, infrastructure configurations, or any repository-bound tools, gsf is here to make your work easier, faster, and more reliable using Git packages, aka Gears.
🔧 Problems It Solves
Have you used versioned .gitlab-ci.yml that require a specific file structure in the repository?
If so, you've probably encountered configuration issues: you forgot to specify
a mandatory parameter, didn't create the right file, and eventually the Pipeline
doesn't work. Or maybe everything was working, and suddenly the Pipeline starts crashing
for no apparent reason - and you waste time figuring out that someone accidentally changed
the startup parameters. And if you need to update an old .gitlab-ci.yml to the latest version,
you often have to manually migrate through multiple versions.
gsf solves all of these problems by automatically managing your config file version and structure, eliminating all of these errors and saving you a lot of work:
-
Reduced manual work
Engineers no longer need to handle installation or updates manually — this is done by the package developer, who knows all the details. -
Version management
The package manager supports migrations between versions. When updating, it automatically performs intermediate steps, ensuring no errors occur from skipping versions. -
Preserving user changes
During template generation, the tool carefully compares files to avoid overwriting user-made changes. -
Security and control
The state of all installed packages is stored in a special.state.yamlfile. The data inside is hashed to prevent unauthorized changes or misuse.
🌟 Key Features
-
Works only with repository branch content
The manager operates exclusively within branches, managing the repository’s content without altering branches, commits, or other repository elements. -
GitLab-specific support
The current implementation is tailored to work with GitLab repositories. -
Package installation
Quickly add new tools or configurations to a repository. -
Package updates
Ensure smooth migrations between versions. -
Package removal
Completely remove configurations and tools without leaving traces. -
Variable management
Add or update variables in CI/CD systems like GitLab. -
Template generation
Create configuration files while considering existing settings and user changes. -
Developer interface
Provides API and tools for package developers to define how their packages are installed, updated, and removed. This ensures that package developers can define migration steps and other actions with precision.
🎯 Key Beneficiaries
DevOps engineers, SRE engineers and other professionals working with GitOps repositories, for example, configuring projects linked to ArgoCD, GitLab CI/CD, or similar tools.
📦 Install
See Installation Guide.
📃 Docs
Get started with the Quick Start Guide or plunge into the complete documentation.
🤝 Contributing
-
CODE-OF-CONDUCT.md
This document outlines the expected behavior for everyone interacting with the project. It fosters a respectful and inclusive environment for developers, contributors, and users. -
CONTRIBUTING.md
This document acts as a guide for anyone interested in contributing to the project. It clarifies the contribution process and helps maintainers manage contributions effectively. -
SECURITY.md
This document focuses on security practices and reporting vulnerabilities. It aims to promote a secure development environment and responsible handling of security issues.
🔄 Changelog
Detailed changes for each release are documented in the TBD.
✒️ License
1 maintainer
Metadata
1 maintainer
Release files for qubership-git-system-follower 0.6.29
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| qubership_git_system_follower-0.6.29.tar.gz | 77.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qubership_git_system_follower-0.6.29-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 207.0 kB
Release files / qubership_git_system_follower-0.6.29.tar.gz
| Download URL | qubership_git_system_follower-0.6.29.tar.gz |
|---|---|
| Size | 77.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32a5cc1082c0bde24f596556031fcba501f39413abc62ed651c482e8da79fe2a
|
|
BLAKE2b-256 checksum How to use checksums |
88a618dc67b595e47b4bd880af1c7359e9d7c868e4df1a7d33728f8002f3eedb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 7, 2026.
Transparency logRelease files / qubership_git_system_follower-0.6.29-py3-none-any.whl
| Download URL | qubership_git_system_follower-0.6.29-py3-none-any.whl |
|---|---|
| Size | 129.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e828ab90cfb7755431d70b4af5abc095b78a6eb34272ca8c4a1b9ddd99ee6c5b
|
|
BLAKE2b-256 checksum How to use checksums |
ee6402837ee2cb4590114de51c0149832fdcf58eb5875a86fb0f3c497ec316a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 7, 2026.
Transparency log
