Your comments
SmartGit already greatly eases this process, just not using the prior commit select list.
Configure SmartGit:
- Set SmartGit preference Low-level properties "git.rebaseInteractive.autoSquash" to "true".
- Set SmartGit preference Low-level properties "log.useCommitMessage.prefix" to "fixup! ". note the space after !
Then can:
- Select the commit to fixup, press Ctrl+Shift+k (from graph or log window).
- See SmartGit populate the Commit view with the commit message prefixed with fixup!.
- Commit.
- Select the commit to rebase interactive from and do it.
- See SmartGit has autosquashed.
Great idea to add context as I see multiple people struggle with this.
Yes, good one - I've encountered temporary confusion by the red highlighting!
Use Window menu: Window -> Repositories
Note the Ctrl+Shift+1 keyboard shortcut.
Also, if you are using the "Standard Window", I highly recommend using the "Log Window". It's Repositories View and functionality is excellent and much more functional.
Are you aware of the "Repositories View"? It lists the repos with a colorized indicator showing its current branch's commits status (incoming and/or outgoing commits available). The repository name is not colorized, but the indicator is.
> A button in the SmartGit PR dialog like "Create on GitHub"
Yes!! I think this is a great idea. I too strongly prefer the SG Create PR dialog and don't want to launch to separate app (browser page) to complete. This idea allows best of both worlds - when the dialog "isn't enough", the quick access to the Git product's web page solves the problem.
In addition to a view/edit dialog, I suggest also adding the branch description to the tool tip.
Displaying in the Branches view may be difficult to display well, so I do not expect it there.
Wondering if this feature is anywhere on the implementation planning radar? It's one of the key usability features we encounter on a daily basis.
I suggest adding a "Commit Message Preview" box showing the resulting commit message.
Customer support service by UserEcho
Agreed on that Thomas, thinking could add the info in the header above the diff w/the existing info.