Skip to main content

Ticketeer Quality assurance Coverage Status

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.

  • message
    • location - where to insert ticket id into commit message (title or body).
    • template - template to use when inserting ticket id into commit message. Must include {ticket} variable.
  • ticket
    • format - format of ticket id (numeric, alphanumeric, alphanumeric-small, alphanumeric-caps).
    • allow-empty - allow empty ticket id. If set to false, commit will be aborted if branch name doesn't contain ticket id.
  • branch
    • format - 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-openbsd 0.1.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ticketeer-openbsd 0.1.5
File Size Uploaded Provenance Actions
ticketeer_openbsd-0.1.5.tar.gz 2.6 kB Without provenance Details for ticketeer_openbsd-0.1.5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for ticketeer-openbsd 0.1.5
File Interpreter ABI Platform Actions
ticketeer_openbsd-0.1.5-py3-none-any.whl Python 3 none any Details for ticketeer_openbsd-0.1.5-py3-none-any.whl

Total release size: 5.3 kB

Release files / ticketeer_openbsd-0.1.5.tar.gz

Download URL ticketeer_openbsd-0.1.5.tar.gz
Size 2.6 kB
Tags Source
SHA-256 checksum
How to use checksums
5e97e93c018e5416c4e5be74779af700ad6266d6c383cdcf54fa2dd6b98ac14e
BLAKE2b-256 checksum
How to use checksums
f037f86fbc92f7298da04249af8a0f8c835ea3b3f203a00e8921f9906da062d1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.0.1 CPython/3.13.1

Release files / ticketeer_openbsd-0.1.5-py3-none-any.whl

Download URL ticketeer_openbsd-0.1.5-py3-none-any.whl
Size 2.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b7fe1574a7f91a86736f58fe1efc9124ffc01bde045981064d758969fff3ae4f
BLAKE2b-256 checksum
How to use checksums
0cdfec0f52ad8d24c1d598462f051339387c6814c3872659c08c6034397829fa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.0.1 CPython/3.13.1

Security for ticketeer-openbsd 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page