Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(conventionalcommits): always use h2 #787

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Mesteery
Copy link

@Mesteery Mesteery commented Apr 8, 2021

Now H2 is used all the time whether it is a patch or not.
Before an H3 was used when it was a patch, but this is bad, because what is supposed to be the title is of the same level as its content (the changelogs sections), so the title (when it was a patch) was hardly differentiable from its content (same title level: H3).
Moreover it could avoid bugging tools that are based on the title level.

@Mesteery Mesteery force-pushed the patch-1 branch 2 times, most recently from 7674543 to 4dfa5ce Compare April 8, 2021 21:50
Now H2 is used all the time whether it is a patch or not.
Before an H3 was used when it was a patch, but this is bad,
because what is supposed to be the title is of the same level as its content (the changelogs sections),
so the title (when it was a patch) was hardly differentiable from its content (same title level: H3).
Moreover it could avoid bugging tools that are based on the title level.
@bcoe
Copy link
Member

bcoe commented Apr 30, 2021

@Mesteery this would be a breaking change. Perhaps you could instead pass in a custom template for your use case?

@Mesteery
Copy link
Author

Yes and no. It's for release-please.
Personally I think that the level of the titles should be well respected: the main title should always be superior to the others, never on the same level.

@bcoe
Copy link
Member

bcoe commented May 5, 2021

@Mesteery funny enough, I think for release-please we pass our own templates, so this wouldn't actually correct the template in its case.

@Mesteery
Copy link
Author

Mesteery commented May 5, 2021

https://github.com/googleapis/release-please/blob/37f4ec236be3bd99e74162a0cc16acd47042528f/src/conventional-commits.ts#L206 is using conventional-changelog-conventionalcommits (except for Ruby releaser which use custom templates).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants