Skip to content

security: require approval for every external fork workflow run - #557

Open
Jubilee-001 wants to merge 1 commit into
Sub-Rosa-Issue:mainfrom
Jubilee-001:security/487-fork-approval-policy
Open

Jubilee-001 wants to merge 1 commit into
Sub-Rosa-Issue:mainfrom
Jubilee-001:security/487-fork-approval-policy

Conversation

@Jubilee-001

Copy link
Copy Markdown

Summary

  • Sets the repository fork pull request workflow approval policy to all_external_contributors.
  • Documents the policy, its effect on organization members and trusted internal collaborators, and the secret-access boundary.
  • Adds documentation links from the README and CI guide.
  • No workflow file changes are required.

Verification

  • GET /repos/{owner}/{repo}/actions/permissions/fork-pr-contributor-approval returns {"approval_policy":"all_external_contributors"}.
  • Default workflow token permissions are read and can_approve_pull_request_reviews is disabled.
  • All workflows use pull_request (not pull_request_target), declare permissions: contents: read, and contain no secrets.* references.
  • node scripts/check-links.js passes.

Closes #487

…osa-Issue#487)

- Set the fork PR contributor approval policy to all_external_contributors
- Document the setting, internal-user access, and secret boundaries
- Link the security configuration from the docs index and CI guide
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

security(high/easy): require approval for every external fork workflow run

1 participant