conventional-changelog-conventionalcommits: Patch version headings shouldn’t be a different size
See original GitHub issueSame as #214, but for conventional-changelog-conventionalcommits. Heading levels indicate a structure. Patch versions should use ## <small>
instead of ###
, as @marcysutton pointed out.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:8 (1 by maintainers)
Top Results From Across the Web
why are patch version headings a different size? #214 - GitHub
I noticed patch version headings are a different size from major and minor ... Patch version headings shouldn't be a different size #867....
Read more >Headings | Web Accessibility Initiative (WAI) - W3C
Headings with an equal or higher rank start a new section, headings with a lower rank start new subsections that are part of...
Read more >Heading levels should only increase by one | Axe Rules
Usually, the best practice is to start the main content of a web page with a level 1 heading element ( h1 ),...
Read more >Why your headings don't match your Table of Contents
I am using Styles for my document headings in my appellate brief. But, even though my Heading 1 is all caps, it shows...
Read more >Heading off confusion: When do headings fail WCAG? - TPGi
Multiple headings with the same text Headings should be clear and descriptive. According to Understanding Success Criterion 2.4.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Actually, the whole idea of using higher-level headings for major releases is a bit strange here, because a heading in a text document is meant for what follow below. However, with the reverse sorting, the structure created here puts the previous releases into the section created by the next version, e.g.:
Why are 1.5.17 and 1.5.18 part of the section opened by the 2.0.0 heading. That doesn’t make any sense with this sorting.
Thank you all. I’ve been waiting for this fix!