I suggest you ...

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.

9 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Dominic Amann shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

4 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
  • Dominic Amann commented  ·   ·  Flag as inappropriate

    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?

Feedback and Knowledge Base