Account-level default for "Approval for running fork pull request workflows" on personal accounts

[hamzahamidi]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Workflow Configuration

Discussion Details

Request

Let personal accounts set a default for approval of fork pull request workflows, matching the organization-level setting.

Current behavior

• Organization owners can set the policy once under Settings, Actions, General, and new repositories inherit it.
• Personal accounts have no account-level Actions setting. Each new public repository starts on “Require approval for first-time contributors.”
• “Require approval for all external contributors” can be set per repository through the UI or PUT /repos/{owner}/{repo}/actions/permissions/fork-pr-contributor-approval.

Why it matters

With the default, an outside contributor needs approval only for a first pull request. After one merged PR, later fork PR workflows from that contributor can run without review. Maintainers who want every external contributor reviewed must update each new repository. A repository remains on the default until someone changes it.

Proposal

Add a personal-account setting with the same three options as the organization policy, applied to repositories created after the setting is enabled. An option to apply it to existing public repositories would also help.

Current workaround

Run gh repo create, then call the API endpoint above for the new repository.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐