Rebase error "This branch cannot be rebased due to too many changes" #51612
Replies: 61 comments 37 replies
-
I'm observing the same issue for a PR with 1 commit, 1 file, and +12 changes. Thankfully I can squash and merge which works fine, but I would like to understand why I am seeing this error. |
Beta Was this translation helpful? Give feedback.
-
I'm also seeing the same issue, only for me, not others working in the repo, but even on branches with one file and +1 line change. |
Beta Was this translation helpful? Give feedback.
-
I'm facing this issue too in my PR and the target branch is protected. Did you have any news about this problem? |
Beta Was this translation helpful? Give feedback.
-
As of today this seems to be working as expected again. No more mentions of too many changes. |
Beta Was this translation helpful? Give feedback.
-
Same problem here. |
Beta Was this translation helpful? Give feedback.
-
See it at Goooler/compiler-explorer#3. |
Beta Was this translation helpful? Give feedback.
-
Same problem here for only 1 commit, 1 file, +8 lines. |
Beta Was this translation helpful? Give feedback.
-
The workaround suggested by @aimee-esler worked for me : https://github.com/orgs/community/discussions/51612#discussioncomment-6554628 |
Beta Was this translation helpful? Give feedback.
-
Thank you @aimee-esler 🚀 |
Beta Was this translation helpful? Give feedback.
-
This is blocking all my prs now and have no workaround. Above workarounds don't work. To reproduce I just amend my commit :( |
Beta Was this translation helpful? Give feedback.
-
Same here. Nothing that was suggested here works. |
Beta Was this translation helpful? Give feedback.
-
Same, seems like this issue started to appear since yesterday incident https://www.githubstatus.com/incidents/mbvjmqbcb1xk |
Beta Was this translation helpful? Give feedback.
-
Same here. We never had this issue and it started to appear today. |
Beta Was this translation helpful? Give feedback.
-
Same here. Please could you provide some update or link to incident. |
Beta Was this translation helpful? Give feedback.
-
Same for me, 1 little commit. Rebasing/squashing locally does not help. |
Beta Was this translation helpful? Give feedback.
-
I have the same issue also right now. I tried to open and close the PR, and it doesn’t effect Do you know what we should do? |
Beta Was this translation helpful? Give feedback.
-
An possible workaround is:
|
Beta Was this translation helpful? Give feedback.
-
Got the same here for +10,-9 changes ! As some pointed out by some, this simple workaround works fine :
Not the first time I use this trick to fix some PR issues by the way, it's quite useful |
Beta Was this translation helpful? Give feedback.
-
Changing the base branch did not work for me, closing the branch, removing the branch, restoring the branch and re-opening did not work either. Creating a new branch from main and cherry picking a commit did also not work. Ended up merging it with the mobile app :/ |
Beta Was this translation helpful? Give feedback.
-
Workaround fix: GoTo Edit -> change base branch to something other than master --> change the base branch back to master. |
Beta Was this translation helpful? Give feedback.
-
+1 Same here; with a |
Beta Was this translation helpful? Give feedback.
-
Out of the blue this happened again today. Thankfully squashing and merging still works as a workaround but it's still unclear as to what's causing this. |
Beta Was this translation helpful? Give feedback.
-
Anybody else seeing this again today? |
Beta Was this translation helpful? Give feedback.
-
We experience this today. These workarounds do not work:
We basically cannot merge any PR because merging is disabled in our repo. |
Beta Was this translation helpful? Give feedback.
-
@mariorod @kdaigle can you please take a look into why the Pull Requests team is refusing to fix this long-standing critical bug? It has been open since March 2023 and is a showstopping bug for many users of GitHub as it makes it impossible to rebase PRs using the UI. Reproduction Steps
Sort-of WorkaroundYou can sometimes get the PR out of this state by forcing GitHub to "refresh" the PR by doing the following: |
Beta Was this translation helpful? Give feedback.
-
I just hit this today. This is frankly stupid. and its a 1 file change, a few lines of code, a fix commit. |
Beta Was this translation helpful? Give feedback.
-
This just happened to me and none of the above suggested solutions work. Can this please get some attention? |
Beta Was this translation helpful? Give feedback.
-
It's happening for me today and none of the workarounds seem to help. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Just wanted to give my 1 cent here: we also had this issue with one of our repos; GitHub's support was able to resolve this for us very quickly. So, if you have a support contract, just ping them as looks like it's a per-repo fix that they need to do there. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I have a Pull Request that got this error when trying to "merge & rebase"
The repository has the policy to only be able to "merge and rebase", and the target branch is protected, so we are a bit stuck !
Before merging this by force with an admin, I would like to try and understand why we are getting this error !
Are there any hard limitations (I did not find any) that we have to be mindful of ?
Like number of commit, of changes, of files changed ?
For the record, here are these metrics for the problematic PR:
We have PR with more changes that were able to rebase without any issue ! (32 commit, 1500 files with +/-15,000 changes).
Beta Was this translation helpful? Give feedback.
All reactions