ci: post code-review-graph comments from a trusted workflow_run - #64
Merged
Conversation
Fork pull_request runs get a read-only GITHUB_TOKEN, so the in-job sticky comment 403s. Keep analysis unprivileged and publish from main.
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
workflow_runonmain.pull_requestruns get a read-onlyGITHUB_TOKEN, which made the in-job Upsert sticky PR comment step 403 on PR #63.Why
Same-repo PRs already succeeded. Contributor fork PRs cannot write comments from the analysis job; publishing from the default branch restores the sticky comment without
pull_request_target.Test Results
Backend
Tests: 128 passed, 0 failed, 0 skipped (0.40s)
Coverage:
Frontend
Tests: 55 passed, 0 failed, 0 skipped (3.05s)
Coverage:
Quality Gates
Complexity
Static Analysis
Security
Checklist
./scripts/quality-gates.shpasses locallyMade with Cursor