git-tagup
Find and tag Git commits based on version numbers in commit messages.
If you're like me, you often add the version number for a commit into the commit message itself, something like:
$ git commit -m "Bump version to 2.1.5"
If you're still like me you probably forget to create a tag for the new version and push it to the remote repository. I end up having projects that have many un-tagged commits from months or years ago that never get real tags.
I created git-tagup to conveniently search through the active branch in a Git repository
and find un-tagged commits containing version numbers in the commit message. For each one
it finds, the tool asks the user whether they want to create a tag for it.
Currently only SemVer versioning format is supported, but I'm happy to take requests for other formats.
Happy tagging!
Requirements
- Python 3.6 or greater
- Pip (Package manager for Python)
Quickstart
- Install
git-tagup:
$ pip install git-tagup
- Browse to the Git repository you want to add tags to - this is usually your project root directory containing the
.gitdirectory:
$ cd path/to/project/root
- Run the program:
$ git-tagup
-
If version numbers are found in the commit messages, answer the prompts with a
yto create the tag ornto skip it. -
Don't forget to push the new tags to your remote when done!
$ git push --followtags
Example
$ cd path/to/project/root
$ git-tagup
Create the tag 'v0.1.1' for commit message 'Bump version to 0.1.1'? (y/n/q): n
Create the tag 'v0.1.2' for commit message 'Bump version to 0.1.2'? (y/n/q): y
Create the tag 'v0.1.3' for commit message 'Bump version to 0.1.3'? (y/n/q): q
Installation
$ pip install git-tagup
Learn More
Learn more about this project on the git-tagup project page.
Authors
- Jacob Stopak - on behalf of Initial Commit
Metadata
Release files for git-tagup 0.1.2
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 |
|---|---|---|---|---|
| git-tagup-0.1.2.tar.gz | 3.4 kB | Without provenance | Details for git-tagup-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| git_tagup-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for git_tagup-0.1.2-py3-none-any.whl |
Total release size: 7.5 kB
Release files / git-tagup-0.1.2.tar.gz
| Download URL | git-tagup-0.1.2.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f8e139cbe2bbc078bc6ae7005ce9745b06daf9be29706e417b3ecaf06faf8d2c
|
|
BLAKE2b-256 checksum How to use checksums |
1e853e0c7b839959202e5a1e3dfbad1c658001f83daae00301798af5b07ebc50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.1.2 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.7.3
|
Release files / git_tagup-0.1.2-py3-none-any.whl
| Download URL | git_tagup-0.1.2-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
906930a219119a4ea00f33e8adde8459272558bedf087045cfac6da05b31183f
|
|
BLAKE2b-256 checksum How to use checksums |
e132a1d4f2dd7be5a63e5c8712e0189ec6316c7225cde1bd6fc8d39d3e6c0e4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.1.2 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.7.3
|
Security for git-tagup 0.1.2
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.