Preventing users from inadvertendly unchecking files during a commit/conflict merge
By alex.nola... on August 26, 2014 23:05 (imported from Google Code)
What steps will reproduce the problem?
On any workflow
- Produce a conflict
- Resolve the conflict
- Commit merge
What is the expected output?
It would be helpful especially for beginners if the list presented during the commit merge conflict is read only and allow editing only through a checkbox.
(please see screenshot)
What do you see instead?
Right now users are presented with their changes along with others that are part of the commit merge. From years of experience, this causes users to start unchecking other files causing other changes to get lost. If you could prevent this with the UI, it would be great.
What version of TortoiseGit and msysgit are you using?
On what operating system?
Please provide any additional information below.
This is an enhance request which could be helpful to newcomers and it could reduce the number of "bad commit" merges which can lead to hard to troubleshoot bugs.
Please do consider.