cmem-plugin-git
Read files from a git repository and commit files back into one.
This is a plugin for eccenca Corporate Memory. You can install it with the cmemc command line client like this:
cmemc admin workspace python install cmem-plugin-git
Tasks
- List Git files lists what a repository holds at one revision, without transferring any file content.
- Download Git files reads the selected files and hands them to the next task in the workflow.
- Upload Git files commits the files of the preceding task into a folder of a repository and pushes them.
All three talk to a repository over HTTP(S) with an access token, work on the objects of the repository rather than on a checkout, and therefore transfer only what they were asked for. Git LFS content, SSH remotes, merge and pull requests, tags and repository history are out of scope. A file uploaded into a path the repository tracks with Git LFS is committed as ordinary content rather than as an LFS pointer.
Access rights
The tasks speak the git HTTP protocol only and never call a forge API, so the token needs repository access and nothing else.
| Task | GitLab scope | GitHub fine grained token |
|---|---|---|
| List Git files | read_repository |
Contents: Read-only |
| Download Git files | read_repository |
Contents: Read-only |
| Upload Git files | write_repository |
Contents: Read and write |
A public repository needs no token at all. The user name sent alongside the
token is ignored by GitHub and checked by GitLab, so it defaults to
gitlab-ci-token, which GitLab accepts for a repository token. On GitLab the
token's role has to
allow pushing to the target branch as well, which a protected branch restricts
to maintainers by default. Upload Git files offers a Check connection
action that asks the server for a write handshake without pushing anything, so
an insufficient token shows up while the task is being configured.
Release files for cmem-plugin-git 1.0.0
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 |
|---|---|---|---|---|
| cmem_plugin_git-1.0.0.tar.gz | 27.2 kB | Without provenance | Details for cmem_plugin_git-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cmem_plugin_git-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for cmem_plugin_git-1.0.0-py3-none-any.whl |
Total release size: 59.1 kB
Release files / cmem_plugin_git-1.0.0.tar.gz
| Download URL | cmem_plugin_git-1.0.0.tar.gz |
|---|---|
| Size | 27.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73c3c5e20acefb672a7e21109147eb658225973d46fa7c558f3df189d9734b36
|
|
BLAKE2b-256 checksum How to use checksums |
656193f245c84e36ef77debf1b829f15dba426353971ab2ee4921cbf026ca76d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.3.3 CPython/3.14.2 Darwin/25.2.0
|
Release files / cmem_plugin_git-1.0.0-py3-none-any.whl
| Download URL | cmem_plugin_git-1.0.0-py3-none-any.whl |
|---|---|
| Size | 31.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6976f930ecd24a09c244b01f6310884b8d75fc05013a6d28bcad66e55865e02
|
|
BLAKE2b-256 checksum How to use checksums |
711c807eb318381de33f99b9543cf44c681a241cfc97a83e17c4e1007f0b392c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.3.3 CPython/3.14.2 Darwin/25.2.0
|
Security for cmem-plugin-git 1.0.0
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.
