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
I am trying to generate a changelog for unconventional commits. The commits may potentially contain more than one change, and I would like to use the commit parsers to grab each relevant part and make a separate entry for them in the changelog.
Steps To Reproduce
Configuration like this
{% else %}\
## [unreleased]
{% endif %}\
{% for group, commits in commits | group_by(attribute="group") %}
### {{ group | striptags | trim | upper_first }}
{% for commit in commits %}
- {% if commit.scope %}*({{ commit.scope }})* {% endif %}\
{% if commit.breaking %}[**breaking**] {% endif %}\
{{ commit.message | upper_first }}\
{% endfor %}
{% endfor %}\n
"""
footer = """
<!-- generated by git-cliff -->
"""
# remove the leading and trailing s
trim = true
[git]
conventional_commits = false
filter_unconventional = false
split_commits = true
commit_parsers = [
{ message = "^fix:", group = "Fixed" },
]
filter_commits = true
topo_order = false
sort_commits = "oldest"
cd $(mktemp -d)
git init .
git commit --allow-empty -m "Unconventional commit" -m "fix: first line of the commit body"
git cliff
P.S. you can't match on specific fields of the commit since it's unconventional + conventional commit parsing is disabled (conventional_commits=false).
Is there an existing issue for this?
Description of the bug
I am trying to generate a changelog for unconventional commits. The commits may potentially contain more than one change, and I would like to use the commit parsers to grab each relevant part and make a separate entry for them in the changelog.
Steps To Reproduce
Configuration like this
This yields an empty changelog.
Expected behavior
I would the changelog to contain:
Fixed
This is also what happens if I change
to
Screenshots / Logs
No response
Software information
Additional context
No response
The text was updated successfully, but these errors were encountered: