Thoughts on the "Commit" tab, and a request to keep the modal around even as a non-default option

Answered

Started a new project on a fresh install of Webstorm, and discovered the new commit tab. I use the local changes tab pretty heavily (especially with legacy monolithic applications with thousands of files, where the file browser becomes useless), so I may be more sensitive to any changes made than most. I get that JetBrains is trying to merge two similar UIs, but it really makes me nervous having both the list of files and a commit button under them. I don't want to misclick on the commit button instead of a file in the local change list, and I don't want to be constantly worrying about that.

After a while I found that I could return to the commit modal, but I would request that JetBrains at least keeps this option around (and please don't stealthily kill it in a few releases). I prefer keeping the function of the list of changed files separate from committing them, especially as my workflow can include hours or days of interacting with changed files before I'm ready to commit.

0
1 comment

There are no plans to remove the old UI at the moment.

However, it is not clear why "it really makes me nervous having both the list of files and a commit button under them". Could you please elaborate?

In git, commit can be undone without any issues, so even if you accidentally commit, you could undo the commit and restore the state.

Currently, Undo is available in the Log context, but probably adding it to the Successful commit notification would be useful.

 

0

Please sign in to leave a comment.