# Unable to merge Origin PR's

**URL:** <https://forum.cursor.com/t/unable-to-merge-origin-prs/171893>\
**Category:** Bug Reports\
**Tags:** origin\
**Created:** [September 16, 2026, 3:03pm UTC](https://forum.cursor.com/t/unable-to-merge-origin-prs/171893 "2026-09-16T15:03:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sethrubenstein](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/sethrubenstein/32/54040_2.png) [@sethrubenstein](https://forum.cursor.com/u/sethrubenstein)\
**Post date:** [September 16, 2026, 3:03pm UTC](https://forum.cursor.com/t/unable-to-merge-origin-prs/171893/1 "2026-09-16T15:03:37Z")

</div>

### Where does the bug appear (feature/product)?

Somewhere else…

### Describe the Bug

As of this morning, I and none of my team members can merge PR’s in Cursor Origin. We have made no changes to branch protection in the last 24 hours so I’m not sure why this is occurring.

### Steps to Reproduce

1. Go to a PR
2. Click not-green “Merge” button
3. Observe inability to merge pr with note on top “Merging onto a branch with required status checks isn’t available for your account”

### Expected Behavior

Being able to merge pr or at least as the admin use my rights to merge even if checks are not green.

### Screenshots / Screen Recordings

 ![CleanShot 2026-09-16 at 10.57.25 AM@2x.png](https://us1.discourse-cdn.com/cursor1/original/3X/a/e/aef4832d652026b217450bd10d3939e2da311103.png) ![CleanShot 2026-09-16 at 10.57.38 AM@2x.png](https://us1.discourse-cdn.com/cursor1/original/3X/0/4/04a1cf9f2acb9877e89f71075c5f6db34e09e41d.png) ![CleanShot 2026-09-16 at 10.58.58 AM@2x.png](https://us1.discourse-cdn.com/cursor1/original/3X/2/f/2fa4e88ed663949e82426737b038ad4658c54a9b.png)

### Operating System

MacOS

### Version Information

This is occurring on Cursor Web

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [September 16, 2026, 4:41pm UTC](https://forum.cursor.com/t/unable-to-merge-origin-prs/171893/19 "2026-09-16T16:41:15Z")

</div>

Hey @sethrubenstein, thanks for the report, and sorry for the disruption!

It looks like the issue is on our side and I’ve flagged this to the team.

One quick thing that would help us confirm the fix covers your setup:

- Is this a GitHub repo that is being synced to Origin?
- If so, on the GitHub side, is the “Require branches to be up to date before merging” setting for your target branch configured under a classic branch protection rule, or under a ruleset?

---

<div class="post-metadata">

**Author:** ![sethrubenstein](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/sethrubenstein/32/54040_2.png) [@sethrubenstein](https://forum.cursor.com/u/sethrubenstein)\
**Post date:** [September 16, 2026, 5:05pm UTC](https://forum.cursor.com/t/unable-to-merge-origin-prs/171893/24 "2026-09-16T17:05:13Z")

</div>

Hey @Colin ,

1. This _was_ a GitHub Repo being synced. Our plan has been to detach from GitHub and just run native Origin which this morning’s PR merge issue forced us to accelerate.
  1. Once we detached from GitHub PR’s originating on origin now work correctly.

2. On the GH side of things I had gone in and disabled every branch protection rule, setting, whatever that might have been blocking it and it still persisted.