⚙️ [Maintenance]: super-linter reports results in the run summary and a PR comment#54
Merged
Marius Storhaug (MariusStorhaug) merged 1 commit intoJul 2, 2026
Conversation
Marius Storhaug (MariusStorhaug)
added
the
github_actions
Grant the Lint job pull-requests: write so super-linter can post its summary comment on the pull request instead of failing the POST with HTTP 403, and turn on the job step summary. SAVE_SUPER_LINTER_SUMMARY builds the summary that both surfaces render.
Marius Storhaug (MariusStorhaug)
force-pushed
the
docs/fix-super-linter-summary-comment
branch
from
8a41752 to
7ab842a
Compare
Marius Storhaug (MariusStorhaug)
changed the title
2 tasks
Contributor
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Marius Storhaug (MariusStorhaug)
deleted the
docs/fix-super-linter-summary-comment
branch
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.
The documentation pipeline no longer errors when super-linter reports its results. super-linter now publishes its lint summary to both the workflow run job summary and a comment on the pull request.
Fixed: super-linter 403 error on pull requests
super-linter posts a summary comment on the pull request, but the
Lintjob did not grantpull-requests: write, so the comment API call failed withHTTP 403on every pull request:The pipeline still passed, but the error made runs look broken. It was pre-existing on
v8.6.0(logged as a warning); super-linterv8.7.0escalated it to an error and enabled the run summary by default, which also produced a summary-configuration warning.Changed: lint results now appear in the run summary and a PR comment
super-linter now reports to both surfaces:
Technical Details
In
.github/workflows/Docs.yml:Lintjob now grantspull-requests: writeso super-linter can create and update the pull request comment (the permission the403was missing).Lintstep setsENABLE_GITHUB_ACTIONS_STEP_SUMMARY: true,ENABLE_GITHUB_PULL_REQUEST_SUMMARY_COMMENT: true, andSAVE_SUPER_LINTER_SUMMARY: true(the last is required to build the summary that both surfaces render).Note: pull requests opened from forks always receive a read-only
GITHUB_TOKEN, so the comment is skipped there — the run job summary still shows the results.Related issues