Disclaimer: this project is currently only a thought experiment!
This project’s goal is to build a distributed support for modern Git workflows.
While Git has been a DVCS from the start, the fork & pull request model is typical of centralized hosting systems.
In my wildest dream, this project would serve as a proof of concept for the architecture required to replace GitHub with a distributed implementation where anybody can self-host their own repositories without losing the ability to use the now widely appreciated power of pull requests.
The minimal requirements for this system are:
people can trivially customize their Git workflow using Git server hooks for implementing things like:
branch update history;
repository, branch & tag permissions;
deploy on push.
people can browse a mesh of these servers using a “true” REST API.
1 maintainer
Metadata
1 maintainer
Release files for gitmesh 0.3.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 | |
|---|---|---|---|---|
| gitmesh-0.3.0.tar.gz | 14.5 kB | Without provenance | Details |
Release files / gitmesh-0.3.0.tar.gz
| Download URL | gitmesh-0.3.0.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f5b0df7f4f3c7e8a19c4dd6d7c613bd47a97f74f605184d34d0f155e01fdb1b
|
|
BLAKE2b-256 checksum How to use checksums |
bf39fde9cc1cccb41114d3fc988703723132f1215753e2fc2002ebe0db4ed1c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gitmesh 0.3.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.
