Continuous backup and recoverable trash can for Git
The aim of git-blackhole is to connect any of your repositories to a single repository (“blackhole” repository) to which you can push any commits — WIP commits, branches no longer needed, and useless stashes.
There are three main features of git-blackhole:
Continuous backup. You can use git-blackhole to continuously backup commits in background to a remote repository (or actually any repository) called blackhole repository.
Run git blackhole init and then setup post-commit hook to run git blackhole push. See the help of git blackhole push for the details.
By combining with git-wip command, you can backup/share uncommitted changes as well.
Sharing local repository state. Since git-blackhole can push commits and the location of HEAD to the blackhole repository, the state of a repository in one machine is accessible from other machines.
For example, if you forget to push a commit from your desktop (to the usual remote) but want to resume the work from your laptop, git blackhole warp would be helpful.
Recoverable trash can. Use git blackhole trash-branch and git blackhole trash-stashes to remove branches and stashes from the local repository after sending them to the remote blackhole repository. They are stored remotely as ordinary branches so that you can recover them easily.
1 maintainer
Metadata
1 maintainer
Release files for git-blackhole 0.1.0.post1
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 |
|---|---|---|---|---|
| git-blackhole-0.1.0.post1.tar.gz | 15.2 kB | Without provenance | Details for git-blackhole-0.1.0.post1.tar.gz |
Release files / git-blackhole-0.1.0.post1.tar.gz
| Download URL | git-blackhole-0.1.0.post1.tar.gz |
|---|---|
| Size | 15.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcd410e40b9f40479a3aeb85e6098aaa7f862efc110cc1a5988963ec51aab0f2
|
|
BLAKE2b-256 checksum How to use checksums |
44fc1f6f8b1c2c888d9e99751fd224f56503451f05e3848a6a8af4e4b11e27d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for git-blackhole 0.1.0.post1
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.
