Shelveset not auto-deleted

[robe070]

When unshelving a shelveset and checking "Automatically delete shelveset after unshelve" we get this message:

"Shelveset not auto-deleted"

Files were unshelved correctly.

server's sgvault.log does not contain any further information.

Manually deleting Shelveset works fine.

We also get the dialog "Locally modified file" for each and every file in the Shelveset, yet none of them have been touched. This is slow and unnecessary for a large shelveset.

[Beth]

Was the file checked out when you unshelved, or did it check out during the unshelve?

The check for a locally modified file doesn't check to see if the files are different. It just knows that the file currently in the working folder has an edit. To change that behavior, you can go to Vault Tools - Options - Local Files and turn off the option to prompt for modified files.

[robe070]

The files were already checked out.

I already have the option "Prompt before overwriting locally modified files" unchecked!

The main purpose I see for Shelvesets is a nightly backup of uncommitted changes. It doesn't make sense to revert the working folder in that circumstance. Hence they files will be edited and will always get a prompt for each and every file.

Right now I'll be banning developers from using it because I'll just get a ton of flack about it otherwise!

[Beth]

I already have the option "Prompt before overwriting locally modified files" unchecked!

Sorry, I was mistaken on that feature. That one doesn't apply to the unshelve. The unshelve is working as designed, but I can put in a feature request to change it.

Do all the files you have on disk match the shelve? If they do, then there's no reason to unshelve. If you have changes on disk since the shelve, then I could see wanting something to only prompt when the files don't match. Is that maybe what you are looking for?

On the auto-delete, there are a lot of reasons why we would stop and auto-delete. In our manual, http://download.sourcegear.com/misc/vau ... thelp.html, and in the help area in the software, there is a section devoted to unshelving. Or you can see this link to see the reasons: http://download.sourcegear.com/misc/vau ... lvechanges.

You said that the files on disk are edited, but that they match what is in the shelve. The fact that they have an edited status may be what's preventing the auto-delete of the shelveset. That is specifically listed as a reason. Why we do these kinds of things is to try and prevent a user from accidentally losing changes they may need.

[robe070]

I responded to this post yesterday, but somehow its missing...

If I have 20 files in the Shelveset and 2 have changed on disk I'd like to have it to behave like Get Latest Version with a Modified Local File. That is, prompt for the action to take BEFORE getting the files and apply that as appropriate to all the files without further prompting.

But if you have to stick with the current interface, only prompt for the diff files and allow that to be configured so it just overwrites, no propmts at all.

The help indeed indicates that in my situation the edited files have stopped the deletion of the shelveset. But thats academic. It doesn't seem practical. There is no awareness that the work file is the same as the Shelveset file. But anyway, why keep the shelveset when its just been successfully restored? Its now in my work directory. Why is a second copy required? I answered 'overwrite' to each prompt. Its complete. Successful. Why keep the Shelveset?

If I actually modify the file so its different to the Shelveset, there is no difference in behaviour.

And if one of the standard use cases is to uncheck out the Shelveset, why is that not the default when shelving?

[Beth]

But anyway, why keep the shelveset when its just been successfully restored?

I believe we're erring on the side of caution. A user who deletes something accidentally that they may need is an unhappy user.

And if one of the standard use cases is to uncheck out the Shelveset, why is that not the default when shelving?

I can see where this might be confusing. I can certainly put in a feature request to change how the auto-delete with unshelving works.

I have logged a feature request on configuring how edited local files are handled during the unshelve.
F: 15306