Ability to customize commit messages in git-cp
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Shell
- Stars
- 18.1k
- Forks
- 1.2k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
git-cp does not allow to associate commits with a specific GitHub/GitLab/.. issue. For example:
Copy a.txt into b.txt (#1252)
Restore a.txt (#1252)
Duplicate a.txt history into b.txt (#1252)
It might be useful for some teams. For example, we use the following syntax: #1252 Commit message. Here is a sample implementation for this scenario: git-cp
Contributor guide
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.
Research direction
Start with the git-cp entry point and review the linked sample implementation to understand how commit messages are currently formed. Define how users would supply a customizable issue prefix or suffix, then verify that copied commits can include the requested issue reference without breaking existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100