You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wouldn't call the repo large, I'm not experiencing anything described in #1841. It's only the squashing that takes forever. What would be steps to debug what is the bottleneck here to provide a proper bug report? My search didn't yield an issue that contains similar report. Or I'm using the wrong keywords 😭.
It's actually any command that rewrites history, e.g. rebasing yields the same slow result.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I've managed to get myself into a situation where I have ~50 stacked commits, where the last 45 are conflicted.
The issue now is, when I refine commit 1, and want to squash changes into it, this operation takes a long time:
I wouldn't call the repo large, I'm not experiencing anything described in #1841. It's only the squashing that takes forever. What would be steps to debug what is the bottleneck here to provide a proper bug report? My search didn't yield an issue that contains similar report. Or I'm using the wrong keywords 😭.
It's actually any command that rewrites history, e.g. rebasing yields the same slow result.
All reactions