Jig
A command line tool and framework for getting more from the Git pre-commit hook.
What is the Git pre-commit hook? It’s a small script that Git automatically runs right before you commit.
Installation
The Jig command line tool is written in Python, you can write plugins in any language you wish. Install the tool by:
$ pip install jig || easy_install jig
Getting started
You can give Jig a spin in less than 5 minutes
It’s super easy to write your own plugins too
Support
Problems or requests? Create an issue on GitHub.
News
Release 0.1.11 - February 28th, 2015
Removes references to the async Python library which is no longer needed by gitdb. Fixes #11.
Release 0.1.10 - July 23rd, 2014
Fixed references to downloading files from GitHub after a security update redirects all requests to githubusercontent.com
Release 0.1.9 - February 22nd, 2014
Adds a jig sticky command that auto-initializes freshly cloned Git repositories for use with Jig.
Release 0.1.8 - February 1st, 2014
Adds a jig report command allowing Jig to be ran on any Git revision range.
Adds a jig version to show the currently installed version of Jig.
Release 0.1.7 - December 13th, 2013
Fix a missing string to unicode conversion that could cause errors if unicode characters were present in the input sent to plugins.
Release 0.1.6 - April 28th, 2013
jig config command added, allowing plugin configuration settings to be managed.
Release 0.1.5 - April 10th, 2013
jig runnow supports a --plugin option so that only a specific plugin is ran.
jig plugin test has a new --range option to limit the tests ran to a specific set instead of the entire suite.
Release 0.1.4 - March 24th, 2013
Jig commands now include more useful messages.
Periodically checks if installed plugins have updates and prompts to install the latest plugins.
Ignores the .jig directory when running (GitHub Issue #1).
Release 0.1.3 - February 16th, 2013
Makes the indicator between warning messages and stop messages easy to discern at a quick glance.
When Jig runs via the Git pre-commit hook, the output is more pronounced.
Update the plugin test runner to ignore the summary lines at the bottom of the output.
Release 0.1.2 - February 13th, 2013
Support for Python 2.6 when running plugins jig plugin test.
Release 0.1.1 - February 7th, 2013
Upgrade plugins installed from a URL using jig plugin update.
Python 2.6 support.
Release 0.1.0 - April 6th, 2012
Initial release.
1 maintainer
Metadata
1 maintainer
Release files for jig 0.1.11
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 |
|---|---|---|---|---|
| jig-0.1.11.tar.gz | 90.5 kB | Without provenance | Details for jig-0.1.11.tar.gz |
Release files / jig-0.1.11.tar.gz
| Download URL | jig-0.1.11.tar.gz |
|---|---|
| Size | 90.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
88a0f9f2057c432a6c723c5273ce11e8c75eddbe80627a7d8034abc75e1ad6e1
|
|
BLAKE2b-256 checksum How to use checksums |
b4c0a21bf13ba97d1b0f10030673353a539abe569d54d30d6eb66550aa13ea70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for jig 0.1.11
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.
