After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 579593 - GUI for rebase interactive
GUI for rebase interactive
Status: RESOLVED OBSOLETE
Product: gitg
Classification: Applications
Component: gitg
git master
Other Linux
: Normal enhancement
: ---
Assigned To: gitg-maint
gitg-maint
Depends on:
Blocks:
 
 
Reported: 2009-04-20 09:08 UTC by Paolo Borelli
Modified: 2018-05-22 13:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Paolo Borelli 2009-04-20 09:08:37 UTC
Kind of a blue sky wish

It would be very neat to have a gui to do rebase interactive
Comment 1 archengule 2009-05-18 01:13:19 UTC
+1
Comment 2 Aaron LaBella 2014-01-13 17:58:56 UTC
+1 for this ... tortoise git has probably the best interactive rebase that I've seen, and it does some really nice "magic" under the covers.  First, you can select between a variety of options (squash, pick, edit, skip, etc.), and when you do what I call a "squash merge", meaning, you squash all the commits into one (very handy for feature branches), it'll take the new commit message and ammend the last commit so that you get a nice new message, and automatically add the commit hashes as additional detail.  Anyhow, I might not've gotten that 100% right because I haven't used tortoise git in a couple years, but, I know that when I do squash merges in Linux from the command line, it's not quite as intuitive as tortoise git made it.  I think the ultimate goal for an interactive rebase in gitg should be very similar to the tortoise git version.
Comment 3 GNOME Infrastructure Team 2018-05-22 13:01:26 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gitg/issues/4.