Built-in project workflow for approved pull requests does not work

[keikoro]

Select Topic Area

Bug

Feature Area

Projects

Body

The built-in project workflow which allows to auto-assign a status to an approved pull request* seems to be broken – approved PRs are never assigned the selected status.

I imagine this may be related to #55826, "GitHub PR filter not working for review:approved" (from 2023 and still unanswered).

*Project workflows aren't properly documented, so I can't say for sure if "Pull request approved" is indeed what this workflow is known as/called by default or if that's a customisation. The triggering action is described as "When a pull request is approved" in any case.

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

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

[LqhResearch]

Hi keikoro,

Thanks for reporting this issue with the built-in project workflow for approved pull requests. Your observation that approved PRs are not automatically moving to the selected status matches other reports like #55826 regarding "review:approved" filters not working properly.

Here are some important points to consider:

• Known Issue: There have been ongoing problems with GitHub’s project automation triggers related to pull request review states, especially the "approved" review event. This can cause workflows that depend on this trigger to not fire as expected.

• Limited Documentation: GitHub’s documentation on built-in project workflows and automation triggers is indeed sparse, making it hard to confirm if the trigger you are using exactly matches “Pull request approved” or a custom variation.

• Potential Workarounds:

  • Double-check that the workflow’s trigger and filters exactly match the PR’s approval event.
  • Test with simpler triggers or other automation steps to isolate the problem.
  • Consider using GitHub Actions or third-party automation to update project statuses upon PR approval as a temporary fix.

• Next Steps:

  • Monitor GitHub’s public issue trackers for updates on this bug (GitHub PR filter not working for review:approved #55826 and related).
  • You can also report this to GitHub Support for escalation.

[keikoro]

This sounds like it was written by AI.