guet
enable contribution tracking when pair programming with guet
Pair programming is integral part of many software development lifecycles. When pairing, you may want to track each committer's contributions. Using guet enables that functionality without changing the normal git workflow.
Installation
guet can be installed from pypi:
pip3 install guet
Usage
init
Initialize repository for guet tracking.
$ guet init
| Flag | Description |
|---|---|
| --location [path to foler] | Specify directory to create hooks in |
| --alongside / -a | Append -guet to hook file names |
| --overwrite / -o | Overwrite existing hooks |
add
Add a committer for commit tracking
$ guet add p1 "Person 1" person@example.com
| Flag | Description |
|---|---|
| --local | Add users locally to this repository (and create local configuration files |
set
Set committers for current repository
$ guet set p1 p2
Committers set to:
p1 - Person 1 <person1@example.com>
p2 - Person 2 <person2@example.com>
get
Get committers.
$ guet get all
All committers
p1 - Person 1 <person1@example.com>
p2 - Person 2 <person2@example.com>
p3 - Person 2 <person2@example.com>
$ guet get current
Current committers
p1 - Person 1 <person1@example.com>
p3 - Person 2 <person2@example.com>
remove
Remove committer
$ guet remove p1
yeet
Remove guet configurations.
$ guet yeet
| Flag | Description |
|---|---|
| --global / -g | Remove guet configuration from home directory |
Questions
There is a frequently asked questions section with some commonly asked questions.
Contribution
Guidelines for contributions can be found here. Feel free to open an issue if there are problems with guet or you want to submit a feature request.
Metadata
Release files for guet 3.0.1
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 |
|---|---|---|---|---|
| guet-3.0.1.tar.gz | 24.7 kB | Without provenance | Details for guet-3.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| guet-3.0.1-py3-none-any.whl | Python 3 | none | any | Details for guet-3.0.1-py3-none-any.whl |
Total release size: 79.8 kB
Release files / guet-3.0.1.tar.gz
| Download URL | guet-3.0.1.tar.gz |
|---|---|
| Size | 24.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fcbe83e15ace773f0cb40d4252a78c8b16fc23d9a38197886ba18a7819f0f7ee
|
|
BLAKE2b-256 checksum How to use checksums |
9e2c5af41dc8c55928a5db09539eed2b2627f9df273f25abb0040ac20da9b3a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.1
|
Release files / guet-3.0.1-py3-none-any.whl
| Download URL | guet-3.0.1-py3-none-any.whl |
|---|---|
| Size | 55.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c4c0163c4c155ba4298323f27a91c8e1f32c7efc35e5f9cee550966fbe2db12
|
|
BLAKE2b-256 checksum How to use checksums |
7628152fd527abc648211ff11502b5130605063317dd7ea1f7669c5400fad776
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.1
|
Security for guet 3.0.1
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.