Repository navigation
docs: fix outdated permissions and example workflows - #505
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe workflow examples add numbered comment labels, grant contents read access, and restrict thread-comment updates to pull requests from the same repository. The permissions documentation describes contents write for push-event commit-comment operations. ChangesAuto-Fix Comment Labels
Thread Comment Permissions
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to
|
Summary
Docs/code consistency pass against
action.ymland the pinned cpp-linter 1.14.1.docs/permissions.md: thethread-commentspush snippet listedmetadata: read, which is not a valid key in a workflowpermissions:block (metadata read access is always granted). Copying the snippet would fail the workflow. Removed it and merged the footnotes.only-PR-comments.ymlrecipe: addedcontents: read(the job also runs onpush, and checkout of private repos needs it), and only enablesthread-commentsfor PRs from the same repo, matching the README's fork guard (fork PRs get a read-only token, so posting fails).auto-fix.ymlrecipe: the example page lists three annotations, but the YAML had no(n)markers, so they were not attached to any line. Added them.Related Issues
None.
Summary by CodeRabbit
contents: writeas the sole permission for commit-comment actions, with revised guidance on what it allows.