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
gg histedit and gg rebase pass through a bunch of output from git rebase. While some of it is helpful, it's not organized particularly well. Especially after fixing #21, there's a bunch of output suggesting Git commands where there are more idiomatic gg counterparts that have more safeguards. It would be good to extract the same information, and then always run git rebase with --quiet. This will require a bit of research to see what git rebase outputs under different circumstances (e.g. merge conflicts, finishing the rebase, running continue when there are unmerged paths).
The text was updated successfully, but these errors were encountered:
gg histedit
andgg rebase
pass through a bunch of output fromgit rebase
. While some of it is helpful, it's not organized particularly well. Especially after fixing #21, there's a bunch of output suggesting Git commands where there are more idiomatic gg counterparts that have more safeguards. It would be good to extract the same information, and then always rungit rebase
with--quiet
. This will require a bit of research to see whatgit rebase
outputs under different circumstances (e.g. merge conflicts, finishing the rebase, running continue when there are unmerged paths).The text was updated successfully, but these errors were encountered: