Option to make the git commit dialog stay? Follow
I'm almost exclusively using the commit feature within PhpStorm.
I'm also very often commit partial changes (only selected files or patches within files).
Everytime I "commit", the dialog however disappears. But I just might want to make the next one, etc.
Is there a config option to make the commit dialog not automatically appear? Or at least not, when there are still pending changes?
Please sign in to leave a comment.
Just to confirm, what style of Commit dialog are you currently using -- a tool window (down below) or a separate dialog?
(Can be changed via "Version Control | Commit Dialog > "Commit from Local changes without showing the Commit dialog")
In fact, tool window should not disappear after commit if it was already opened at that moment:
> what style of Commit dialog are you currently using
Good question :-)
It's already muscle memory, I press CMD-k and get the "Version control" window (I did make it a separate window, but it can be pinned, etc.) Looks to be the same as CMD-9.
That window starts out at the "Local changes" part, yeah it's the same.
Hmm, strange. I played about around with "pinning" it etc. and I could create a scenario, but can't say how exactly, where with one test it did not disappear. But don't know how to reproduce.
Here is how it looks to me (my full screen window version):
On this screenshot, the commit area is there.
But it does disappear after the commit and can be invoked again with Cmd+K.
The reason why it disappears is that the commit message can be calculated dynamically depending on what file / changelist you have chosen, so keeping an empty/outdated commit area makes little sense, as I see it at least.
But everything else, the file tree and the diff, are still there. Isn't that what you were looking for?
> On this screenshot, the commit area is there.
> But it does disappear after the commit and can be invoked again with Cmd+K.
Yes, but to be clear: the whole window disappears, not just the area.
> But everything else, the file tree and the diff, are still there. Isn't that what you were looking for?
Yes, but as I said, the whole window is closed once I commit and I've to bring it up with CMD-k again.
When I prepare my changes and I want to maybe make 2-6 commits, depending how I want to split the them up, that's a lot of times CMD-k to bring it up, select the changs, commit, repeat.
It's definitely worth a bug report then, but we do need reproduction steps.
I finally figured out what causes the difference, it's how you go about commiting.
Assume the start point is the classical project view (left source code, right editor window):
It's the same "Version Control" dialog, it's "Local changes" tab BUT the commit dialog is there. Even on a partial commit, after the commit it disappears completely.
I sense there is a certain logic to it: if you intent to commit directly via CMD-k, the assumption is "go back from where you came".
But in my case, for partial commits, I would assume the IDE gets "not done yet, not returning".
Do you think that's work a report? Considering this behaviour, I don't think it's a bug per se.
Yes, this can be reported to our tracker. Not a bug, but a usability issue worth checking by VCS team.
kk, created https://youtrack.jetbrains.com/issue/WI-50573 !