fix: keep approve-pr CI test unprivileged - #677
Conversation
Code Coverage OverviewLanguages: Go, C# Go / code-coverage/testThe overall coverage remains at 50%, unchanged from the C# / code-coverage/dotnetThe overall coverage remains at 100%, unchanged from the Updated |
✅MegaLinter analysis: Success
Notices📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
|
|
@cursor review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 98f46a2. Configure here.

Motivation
./approve-pr) with a GitHub App private key and write permissions.approve-praction while ensuring PRs cannot receive real secrets or a write-capable token.Description
test-approve-prjob permissions tocontents: readso it no longer grants write capabilities to PR-run jobs in.github/workflows/ci.yaml.vars.APP_CLIENT_IDandsecrets.APP_PRIVATE_KEYinto the PR-controlled local action and replaced the private key with a non-secret placeholderapp-private-key: dry-run-placeholder.dry-run: trueto theapprove-prinvocation so the test exercises the action without minting an App token or approving the PR.Testing
git diff --check) passed.test-approve-prjob contains neither secret expressions nor write permissions and reported success.yamllint,zizmor,actionlint) could not be executed due to outbound package/download restrictions in the execution environment, so they were not run here.Codex Task