GitHub Pull Request acknowledged that code owner approved the request, but it's still blocked until the code owner approves

[altjx]

Select Topic Area

Bug

Body

This seems like a bug to me. I have a branch ruleset that requires the codeowners' approval prior to a pull request being mergable. However, I am the only codeowner, and I did approve the pull request.

The screenshot below seems to say that I approved it, but also says that it's waiting on me to approve it.

Could this issue be related to read-only vs write permissions? I have admin privileges to the repository, but when I approved the PR, it shows that I approved the changes with read-only permissions. I'm not exactly sure what this means.

FWIW, here's my .github/CODEOWNERS file:

# CODEOWNERS file
# This file defines individuals or teams that are responsible for code in this repository.
#
# Each line is a file pattern followed by one or more owners.
# These owners will be the default owners for everything in the repo.
#
# More information: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

# Global rule - require review from altjx on all files
* @altjx

I'm just a bit confused on what the issue is. Is it because I have more than the required permissions, or is it not recognizing that i have write permissions inherited by admin privileges?

Any help would be greatly appreciated.

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

[tonglil]

Related to: https://github.com/orgs/community/discussions/175951