Commit action should unlock file even if no other changes have been made.
When a file is locked, but no other changes have been made to the file, "Commit changes" becomes active in the interface, but selecting it does not unlock the file (and therefore commit changes remains active). This behaviour also exists in Tortoise, but is equally annoying there.
I agree, performing the unlock operation (by pressing Commit) would be a nice thing to do.
Would also be nice to have "revert and unlock" in one step.
Is this version of the comment clearer?
Dominic Amann commented
Your response / comment seems a little cryptic to me.
Do you mean that instead of "Commit changes" becoming active, that "Unlock" should be active (and not Commit changes), so the user would be able to unlock the file, or do you mean that under the circumstances described, clicking on "Commit changes" should trigger an "unlock" action, and "commit changes" would then become inactive?