feat(scope_configuration): support icon#348
Merged
Merged
Conversation
Re-triggers release-please for changes merged in #336, which used a non-conventional PR title ("Support icon in scope configuration") and was therefore skipped by release-please when generating 2.4.0..2.4.3. The functional change is already in main (a8fea94); this empty commit exists only so release-please picks up the feat in the next release.
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
1 participant
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
Re-triggers release-please for the change merged in #336.
Context
PR #336 (
Support icon in scope configuration) was merged with a non-conventional title. Since the repo uses squash merge, the PR title becomes the only commit message onmain, and release-please parses commits onmainto decide what enters the next release. As a result, thefeatwas skipped across releases 2.4.0 → 2.4.3.The actual code change is already in
mainat commita8fea94. This PR contains an empty commit whose subject follows Conventional Commits, so release-please can recognize the change and include it in the next release PR (bumps minor → 2.5.0).Why an empty commit
main.Follow-up (optional)
Consider adding a PR title validator (e.g.
amannn/action-semantic-pull-request) so future PR titles are enforced — the existing commitlint workflow only validates commits, not the PR title that survives the squash.Test plan
feat(scope): descriptionper@commitlint/config-conventional.feat.