Feature Request: JIRA Ticket as first item of first line
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by tracing the existing -c context-switch handling and the code that assembles the first commit-message line; the issue names no files or tests. Check how an environment variable such as TICKET should interact with the current prefix behavior, then verify that generated commits place its value first when it is set.
Written by the indexing model from the issue text.
Description
I'm 100% sure that I can accomplish this same thing by using the "-c" context switch.
What I want is a system environment variable into which I can set the JIRA Ticket number (or Github issue or whatever ticketting system) and have it always appear as the first item on the first line.
What I think I'm seeing in that location now is the directory name of the repository in all uppercase followed by "-123". but that is not consistent.
If I can setup an envar like export TICKET=xyzzy-123 then every commit I make will have my ticket number on it. When I pick up a new ticker I will change the value of $TICKET.
- Dominant language
- Go
- Stars
- 184
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coder/aicommit
-
Feature: lint PR titlesPossibly taken @mtojek claimed this 721 days ago. Openenhancement
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
schema-drift
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stefanhoth/paperless-ngx-cli#61 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
slavakurilyak/awesome-ai-agents#888 ·
Maintainers usually reply within 1 day
-
enhancement nav-pilot
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
kind/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day