Commit History when using `git release`
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 18.1k
- Forks
- 1.2k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
Hello,
Thanks for these great tools. I was wondering how people are actually using git release with the "changelog" option? My point being, I was expecting either to have the possibility to disable the automatic push to remote in order to commit manually some files such as the changelog; either to see the History.md getting added/staged/committed automatically when using the -c argument.
Is there any way/workflow to allow the generation of the History.md file and getting it commit at the same time? How people are actually using this feature? Am I missing something?
Thanks a lot!
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 by tracing the git release entry point and its changelog and -c handling. Inspect how History.md is generated and how the release is pushed; done means the intended workflow or option for generating and committing History.md is clearly supported and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- cli, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100