Introduction
The monitor extension tracks a directory of hg repositories for changes which are not committed or pushed to the server. The basic use case is for easily tracking a set of diverse repositories for pending changes. Another use is to schedule an e-mail updating on the state of pending changes.
All monitor commands take an optional directory argument and a boolean recurse flag. The default (recurse False) is to recurse one directory, but when recurse is true, monitor searches for all hg repositories under the directory.
In addition, if the mq switch is enabled, then monitor searches for hg repositories in .hgpatches inside each main repository found.
In some ways, this extension provides a much more flexible notion of sub-repositories. There is no tracking of related repositories beyond being in the same sub-directory. Such simplicity can allow a more flexible workflow.
Examples
List changes in repositories directly under the current working directory:
hg monitor
List changes in all repositories under the given directory or directories:
hg monitor --dir=<dir1> --dir=<dir2> --recurse
Pull changes from the default repository for all repositories in the scope of the command:
hg mpull --update
hg mpush
The mbackup command has facilities for backing up uncommitted changes (and unpushed changesets - in the future). It could also be a directory:
hg mbackup --dir=<directory> --remote=<additional backup folder>
Changelog
0.5 - fixed bug with –dir selectors not accumulating when they point directly to repositories – Thanks Piotr Owsiak
0.4 - added email from monitor and extended zipped backup to include outgoing changes
0.3 - added mbackup with zip & copy for uncommitted changes
Future
The monitor command will include the ability to e-mail uncommitted/unpushed changes to an e-mail address:
hg monitor --dir=<directory> --email
Metadata
Release files for hgmonitor 0.5
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 |
|---|---|---|---|---|
| hgmonitor-0.5.tar.gz | 7.3 kB | Without provenance | Details for hgmonitor-0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hgmonitor-0.5-py2.7.egg | Legacy Egg format | - | - | Details for hgmonitor-0.5-py2.7.egg |
Total release size: 23.7 kB
Release files / hgmonitor-0.5.tar.gz
| Download URL | hgmonitor-0.5.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad22620873c78d9876e79733cfec91bda2fa1ca8fab019076214d0d7f272752d
|
|
BLAKE2b-256 checksum How to use checksums |
165e7668d75d732ead667ff3313abcd9115b1906424899a2bfe8932e9725ac7f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / hgmonitor-0.5-py2.7.egg
| Download URL | hgmonitor-0.5-py2.7.egg |
|---|---|
| Size | 16.4 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
ed97dfe6e135d67bc0e600dd7b89130704ffa504bc70f74d1c12757382837cc9
|
|
BLAKE2b-256 checksum How to use checksums |
3175330c34b25fa04febc539b81f0091d449d9ade2883708cea4081204115206
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for hgmonitor 0.5
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.