GitHub "Sync Fork" UI Cannot Function Under Minimal Ruleset Branch Protection

[klondikemarlen]

Select Topic Area

Bug

Body

Summary

The "Sync fork" UI is presented for forked repositories, but cannot function at all when a repository uses a minimal, recommended Ruleset configuration that requires pull requests on the default branch.

There is no bypass actor that represents GitHub’s own fork-sync operation, making the UI action impossible to complete.

This behavior differs from legacy branch protection rules and appears to be an unintended limitation or regression in Rulesets.

---

Expected behavior

For a forked repository:

• The UI presents an action ("Sync fork") that GitHub itself cannot execute
• The failure occurs under minimal, documented branch protection
• No unsupported configuration is required
• No warning or explanation is shown
• No alternative UI path is offered

This violates expected UI behavior: an action should not be offered if it is guaranteed to fail.

---

Actual behavior

• The fork is shown as behind upstream
• "Sync fork" is offered
• The operation fails due to ruleset enforcement
• GitHub provides only a local-resolution message
• No bypass actor exists to allow the operation

As a result, the standard GitHub fork sync UI is unusable when Rulesets are enabled with PR-only enforcement.

---

Reproduction steps

1. Fork a repository.
2. In the fork, enable a Ruleset targeting main.
3. Enable Require a pull request before merging.
4. Ensure no bypass actor exists that represents GitHub’s fork sync.
5. Make upstream main advance.
6. Open the fork’s main branch page and click Sync fork.

---

Impact

• Forces all fork synchronization to happen via manual pull requests.
• Breaks long-standing GitHub fork workflows.
• Makes Rulesets incompatible with expected fork behavior.
• No configuration workaround exists; while it possible to allow admins to bypass branch protection, but this defeats much of the purpose of using branch protection in first place.

---

Notes

This does not appear to be documented, and there is currently no supported way to keep Rulesets enabled while preserving standard fork sync behavior.

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

[riedgar-ms]

I am seeing this too - and I've checked that in my Rules have "Allow Fork Syncing" checked in the Rule which protects main. I can click on "Sync Fork" on the repo landing page and.... nothing happens. Not even an error.