Add a pre-commit hook to expand relative ticket refs to absolute

Open
#123 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
git
Domain
tooling

Research direction

The issue names no file, test, or entry point. Start by locating the repository's commit-hook configuration and checking how commit messages are currently processed; done means relative ticket references are expanded to the correct repository-qualified references without changing unrelated messages.

Written by the indexing model from the issue text.

Description

The hook would possibly change commit messages to ensure absolute ticket refs.

E.g.

  • #27 → jaraco/skeleton#27, if we commit in skeleton,
  • #27 → jaraco/tempora#27, if we commit in tempora.

Addresses commit integrations mismatch.

Dominant language
No language data
Stars
152
Forks
38
Avg merge
6h 27m
Merged PRs (30d)
4

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jaraco/skeleton

All issues in jaraco/skeleton

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.