Ticketeer

Utility to insert task ticket id into commit message.
- Simple. Does not need to be configured;
- Environment agnostic. Works with any platform that can run git;
- Fast. Won't slow down your commit process as actions are performed instantly.
Installation
go
go install github.com/mishamyrt/ticketeer@latest
pnpm
pnpm add --save-dev ticketeer
npm
npm install --save-dev ticketeer
yarn
yarn add --dev ticketeer
Usage
Standalone
Ticketeer can be used as a standalone tool. To install hook, run:
ticketeer install
The utility will check for installed hooks and install its own.
Runner
If you are already using runner hooks on your project and want to keep everything under their control, add a ticketeer apply call to your runner configuration.
Lefthook
Add the following to your lefthook.yml file:
prepare-commit-msg:
commands:
append-ticket-id:
run: ticketeer apply
If ticketeer is installed using NodeJS package manager, prefix command with your package manager runner, e.g. pnpm ticketeer apply, yarn ticketeer apply or npx ticketeer apply.
Configuration
Ticketeer is configured by default to be as comfortable as possible for most, but the settings can be overridden. All options are optional (hehe), if you don't specify your own - default value will be used.
messagelocation- where to insert ticket id into commit message (titleorbody).template- template to use when inserting ticket id into commit message. Must include{ticket}variable.
ticketformat- format of ticket id (numeric,alphanumeric,alphanumeric-small,alphanumeric-caps).allow-empty- allow empty ticket id. If set tofalse, commit will be aborted if branch name doesn't contain ticket id.
branchformat- format of branch name (git-flow,git-flow-typeless,ticket-id).ignore- Additional list of branch names to ignore. Default value is["main", "master", "develop", "dev", "release/*"].
Default configuration is as follows:
message:
location: body
template: "{ticket}"
ticket:
format: alphanumeric-caps
allow-empty: true
branch:
format: git-flow
Metadata
Release files for ticketeer 0.1.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 |
|---|---|---|---|---|
| ticketeer-0.1.5.tar.gz | 3.5 kB | Without provenance | Details for ticketeer-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ticketeer-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for ticketeer-0.1.5-py3-none-any.whl |
Total release size: 7.4 kB
Release files / ticketeer-0.1.5.tar.gz
| Download URL | ticketeer-0.1.5.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
edf37fc0b6514590ca0580a8263f011b27b35c784ad4432d70dade2b3eba0910
|
|
BLAKE2b-256 checksum How to use checksums |
af64b3c22bb0cf66fb5d2e48de54c8882ff6e268a5f4ce798048d2d1586f1242
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.13.1
|
Release files / ticketeer-0.1.5-py3-none-any.whl
| Download URL | ticketeer-0.1.5-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b9be9a4b901ea0de6031a5070b682f19761d04f725a09d4cb122517eb877744
|
|
BLAKE2b-256 checksum How to use checksums |
b573c29b767a660803cd1961940c8620dd0cec1eb23952f40ef7eb89db6238f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.13.1
|
Security for ticketeer 0.1.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.