Workflow issue: partial updates

[Ralf]

Ever since the introduction of the 'Shall I update the working copy and retry?' dialog, we've had occasional issues with some of our content creators doing partial updates, which results in cascading errors down the line.

This is the problematic workflow:

1. User uses the "Check for modifications' dialog to look at the changes they've made.

2. User then starts a commit by selecting all the files in the 'Check for modifications' dialog.

3. User sees a Commit Failed! dialog because one of the files they're trying to commit was changed since the last update.

4. User selects 'ok', then is shown the 'Shall I update the working copy and retry?' dialog.

5. User selects 'update', which then only updates the files they had selected in step 2.  Their conflict, however, is automatically resolved.

6. Tortoise then automatically shows the commit dialog again.

7. User selects 'ok', which now commits their changes.

8. User thinks everything is rosy and continues working, doesn't realize that they have a partially updated working copy.

I realize that this issue can be resolved with education/checklists, but we've been bitten several times by this now, simply because humans are humans.  It would be great to have an option to disable the 'Shall I update the working copy and retry?' dialog.  I've tried disabling the "OutOfDateRetry" advanced setting, but it has no effect on this behavior.

Any advice or tips?

Thanks,

Ralf

[Stefan]

Right now, there is no option to change that behavior.

I think there should be several options:
* disable the update completely (but still showing the dialog informing the user that an update is required)
* update always from the WC root instead of just the paths selected for commit
* show the dialog, allow to update but do not reopen the commit dialog (that's what OutOfDateRetry=false does)
* the way it works now

Any options I forgot?

I'll try to implement this soon.

Stefan