Skip to main content

mercurial repository monitoring and handling as a group

Project description

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

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

hgmonitor-0.5.tar.gz (7.3 kB view details)

Uploaded Source

Built Distribution

hgmonitor-0.5-py2.7.egg (16.4 kB view details)

Uploaded Egg

File details

Details for the file hgmonitor-0.5.tar.gz.

File metadata

  • Download URL: hgmonitor-0.5.tar.gz
  • Upload date:
  • Size: 7.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No

File hashes

Hashes for hgmonitor-0.5.tar.gz
Algorithm Hash digest
SHA256 ad22620873c78d9876e79733cfec91bda2fa1ca8fab019076214d0d7f272752d
MD5 5cc3add2fe5bee2c2f88818f3ceaa4f7
BLAKE2b-256 165e7668d75d732ead667ff3313abcd9115b1906424899a2bfe8932e9725ac7f

See more details on using hashes here.

File details

Details for the file hgmonitor-0.5-py2.7.egg.

File metadata

  • Download URL: hgmonitor-0.5-py2.7.egg
  • Upload date:
  • Size: 16.4 kB
  • Tags: Egg
  • Uploaded using Trusted Publishing? No

File hashes

Hashes for hgmonitor-0.5-py2.7.egg
Algorithm Hash digest
SHA256 ed97dfe6e135d67bc0e600dd7b89130704ffa504bc70f74d1c12757382837cc9
MD5 d5b9e56f83be6eadd0962f6230d9e591
BLAKE2b-256 3175330c34b25fa04febc539b81f0091d449d9ade2883708cea4081204115206

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page