Open JesseKPhillips opened 4 years ago
Hi @JesseKPhillips,
Thank you for suggesting this feature! The core
package now supports generating changelog between two tags. Could you provide a few usage examples about your suggestion?
I had something in mind to achieve it but it seems to differ from what you suggest:
gitmoji-changelog --from 1.0.0 --to 2.0.0
I don't always have a tag on a release, I build the version based on the previous tag and commit count.
Most git commands accept tag, hash, branch and some a search so I figured that it would be easiest to pass through.
I suggested the syntax git uses for spanning commits, though they might use three dots.
gitmoji-changelog generate --version 1.8.9 1.7.4...a6cdf5
@bpetetot what are your thoughts on this suggestion?
Yes seems a good idea. If it's done, I think it should follow the git syntax.
@JesseKPhillips are you interested in doing this?
I'm not going to say no, but due to my lack of familiarity in Javascript and other activities I won't expect to get started or finish anytime soon.
I took a quick look at the code but didn't feel I was following along for what I would need to change.
Feature Request to provide commandline options allowing to specific the commits to build a changelog for.
Usage:
gitmoji-changelog generate [--version <version>] <oldest commit>[...latest commit]
This would allow for generating an organized list of commits in the form a changelog at any arbitrary Git reference (branch, hash, tag).
My thought is that I would past this result into the GitLab Changelog of a specific tag.
Git diff doc
git diff [<options>] <commit>...<commit>