Repository navigation
fix(conventional-commits): report PR title errors in job summary - #162
Merged
Merged
Conversation
The sticky comment steps read steps.lint_pr_title.outputs.error_message, but the semantic-pull-request step had no id, so the error comment was never posted. Posting it would also need pull-requests: write, which callers only grant as read. Add the missing step id and write the error to the job summary instead of a PR comment, so no extra permission is required. Also lint this repository's PR titles with the local reusable workflow.
PierreJeanjacquot
force-pushed
the
fix/conventional-commits-step-id
branch
from
September 29, 2026 13:59
2f406ea to
0836a78
Compare
PierreJeanjacquot
changed the title
PierreJeanjacquot
changed the title
jbern0rd
approved these changes
Sep 29, 2026
Contributor
Author
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.
The sticky comment steps read steps.lint_pr_title.outputs.error_message, but the semantic-pull-request step had no id, so the error comment was never posted. Posting it would also need pull-requests: write, which callers only grant as read.
Add the missing step id and write the error to the job summary instead of a PR comment, so no extra permission is required.