Can no longer make new commits during interactive rebase
See original GitHub issueDescribe the bug
Earlier I could start an interactive rebase, and while on a certain commit I could make changes and commit these in Github Desktop. Now (probably after some recent update) this does no longer work, and it doesn’t let me commit anything, only says “Resolve conflicts to continue rebasing <branch>”. Clicking “View Conflicts” shows “All conflicts resolved”
Version & OS
Version 2.5.4, on macOS 10.15.6
Steps to reproduce the behavior
- Rebase branch
git rebase -i master
- Edit a commit.
- Make changes
- Try to commit changes in Github Desktop
Expected behavior
Let me commit changes.
Actual behavior
Cannot commit anything.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:12 (5 by maintainers)
Top Results From Across the Web
git - Can I recover commits lost during interactive rebase?
The entire rebase is undoable ! Just use git reflog to locate the place where you were just before the rebase. It will...
Read more >git-rebase Documentation - Git
With --rebase-merges , the rebase will instead try to preserve the branching structure within the commits that are to be rebased, by recreating...
Read more >Fix a Commit History With Git Interactive Rebase
When the rebase runs, your history will be checked out at that commit. You can then reset the commit, change it as you...
Read more >Introduction to Git rebase and force-push - GitLab Docs
git rebase rewrites the commit history. It can be harmful to do it in shared branches. It can cause complex and hard to...
Read more >Editing a commit in an interactive rebase - Bryan Braun
We can use the “edit” option in an interactive rebase to fix this. I'm going to assume you're familiar with interactive rebases but...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@niik I understand that this is perhaps not the intended way of using the app, but that being said this used to be supported earlier (I did this regularly a few months ago).
If the support is not coming back, I plan to revert back to the latest version where this was supported. I can report at which version it stopped working if that is helpful.
Of course it’d be nice to be able to do ☝️ without the hackiness of this workaround or requiring temporary branch.
How about simply not disabling the UI if it’s an interactive rebase; only disabling and greying out the UI for staging and committing during a Desktop-initiated rebase?
Or re-enabling the staging/comitting UI if the user closes the dialog using its (x) button?
For interactive rebases from the CLI using things like re-ordering and
fixup
, GitHub Desktop does a good job of presenting merge conflicts in a clear way, and the “continue” and “abort” buttons seem to work fine. The only problem I’ve found is that during anedit
, if I close the dialog using (x), all the UI controls are disabled. If they weren’t I could make my commits in the UI, bring back the dialog from the status bar message, press “Continue rebase” and (I think) it’d work just fine.