Automatic dirty working directory shelving for Mercurial
AutoShelve is a Mercurial extension that shelves modified files before applying changes to the repository then unshelve them.
Why would I use it ?
I not sure that there is a valid reason for using it. But it’s a pragmatic solution for durty use cases. Autoshelve will avoid you wasting time until you meet and find a good solution.
- Note:
Shelve operations may be very long for certain repositories. In this cases you may want to disable or enable autoshelve in the configuration file of the repository.
Installation
Install hg-autoshelve using pip:
pip install hg-autoshelve
Then enable the extension in your mercurial configuration file:
[extensions] hgext3rd.autoshelve=
Metadata
Release files for hg-autoshelve 0.1.7
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 | |
|---|---|---|---|---|
| hg-autoshelve-0.1.7.tar.gz | 3.1 kB | Without provenance | Details |
Release files / hg-autoshelve-0.1.7.tar.gz
| Download URL | hg-autoshelve-0.1.7.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1363ff4ea62808ac024916429c38fc84a4a670b2d5efdc38f8a9bfc63d49bd44
|
|
BLAKE2b-256 checksum How to use checksums |
7a306b52e4bdc317523350c4c4302ccc00aa90cea027c3dccfac835dba0c8cbf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.28.1 CPython/3.7.4
|
Security for hg-autoshelve 0.1.7
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.