You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
git-cliff looks amazing for parsing git commits, but sometimes I'd love to have more power over the parsed commit messages (i.e. the Context that's passed to Tera) instead of being forced to use a Tera template to generate my changelog.
Describe the solution you'd like
Would it be possible to have an option added to git-cliff that would output the parsed commits as a normal JSON file without first passing it through a Tera template?
The text was updated successfully, but these errors were encountered:
Perfect, it works beautifully, thank you so much! One question I have is whether the warning "git_cliff > Changelog body is not specified, using the default template" should still be displayed when the --context flag is used. If I understand correctly, the body tag should be redundant when using --context (Correct me if I'm wrong!)
Perfect, it works beautifully, thank you so much! One question I have is whether the warning "git_cliff > Changelog body is not specified, using the default template" should still be displayed when the --context flag is used. If I understand correctly, the body tag should be redundant when using --context (Correct me if I'm wrong!)
Is your feature request related to a problem? Please describe.
git-cliff looks amazing for parsing git commits, but sometimes I'd love to have more power over the parsed commit messages (i.e. the Context that's passed to Tera) instead of being forced to use a Tera template to generate my changelog.
Describe the solution you'd like
Would it be possible to have an option added to git-cliff that would output the parsed commits as a normal JSON file without first passing it through a Tera template?
The text was updated successfully, but these errors were encountered: