ci: reject leading ticket tags in commit headers (release-please parseability) - #809
Merged
Conversation
HerbertJulio
approved these changes
Jul 27, 2026
gdsantana
approved these changes
Jul 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
[NO-ISSUE] fix: …and silently released nothing (run 30270134693 —commit could not be parsed … unexpected token ' ' at 1:11). Its parser is not configurable (the old.releasercparserOptsdied with ci: replace semantic-release with release-please (Release PR model) #798).fix(webkit): [ENG-1234] subject. No ticket → no tag:[NO-ISSUE]is dead characters (100-char budget, changelogs) and is rejected.commitlint.config.jsnow matches release-please's parser exactly, with two inline rules guarding the migration:header-no-leading-ticket(old leading-tag form → actionable error) andsubject-ticket-tag(well-formed[ABC-123]only;[NO-ISSUE]→ "omit the tag entirely").Notes
CONTRIBUTING.md§ Message shape / Local enforcement,DOC_LINTS.md§10 (header anatomy + ❌/✅ examples), and the/open-pr+/create-branchprompts. Every example was verified against the real commitlint config.CONTRIBUTING.md§ Releasing also corrected: it still describedsemantic-release; it now documents the release-please Release PR model (ci: replace semantic-release with release-please (Release PR model) #798).ci/docs). Old-form commits were already release-inert — they now fail loudly at commit time instead. The release missed by fix: use @aziontech/theme/animations imports; move vue-tsc to devDependencies #804 will be recovered separately (release-pleaseBEGIN_COMMIT_OVERRIDEretrofit).**/CHANGELOG.mdfrom the Prettier gate (.prettierignore, same precedent ascatalog.json): release-please commits changelogs via the GitHub API in its own markdown style (*bullets), which was failing theLinting & Formattingcheck on Release PR chore: release main #810. Verified against the realrelease-please--branches--maincontent.