[Feature Request] Distinguish GITHUB_TOKEN being used to create pull requests v.s. approve requests.

[AlexKeySmith]

Why are you starting this discussion?

Product Feedback

What GitHub Actions topic or product is this about?

Workflow Configuration

Discussion Details

It would be great if the GITHUB_TOKEN could be configured to create pull requests, but not approve them.

Currently, the setting is too coarse-grained (both create and approve), and understandably, some organizations (like mine) have disabled it at the organization level.

However, it makes sense for a bot to create pull requests—for example, to increment a release number or auto-generate documentation—while still requiring a human to perform the final approval.

I understand there may be concerns about pull request triggers causing loops, but since this setting now exists, I assume those concerns have already been addressed.

This is typically worked around by creating a PAT, but it's a shame to have to do that and a pain if a service account needs creating first.

[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. ⭐