Version control: pruning branches?

laird_broadfield

Couple of related I-can't-find:
Although I can delete a workspace, it doesn't appear to be possible to delete entire branches.
Indeed, neither can I delete intermediate versions.

Am I missing it, or is it not there?

3dcad

There is no purge for the history.
See earlier thread: https://forum.onshape.com/discussion/755/how-to-clear-history

shashank_aarya

@laird_broadfield Versions are always read only because they indicates the revision of document hence cannot be deleted. In any other PDM systems such as Windchill, Team center they also have same things for their revisions. e.g. Revision A is derived from initial release, Revision B is derived from revision A and so on for next revisions. In this case deleting the revision A will not make any meaning for revision B since it has reference from A. So we cannot delete any revisions. Same concept is used in Onshape as versions.

traveler_hauptman

@shashank_aarya ...Maybe... Incremental versions are not always used and its very possible that Onshape is not using them. No need. 

_Ðave_

You can delete an entire branch only if there hasn't been any saved versions within it. You can't delete a saved version. You can also make a copy of the main or any  workspace/branch. This will create a copy without any other branches and no saved versions, unfortunately all other branches and all saved versions will be removed.

shashank_aarya

traveler_hauptman said:

@shashank_aarya ...Maybe... Incremental versions are not always used and its very possible that Onshape is not using them. No need. 

Suppose any version before latest is deleted, it would difficult to find the last modification before making the new version. Most of the times information from previous versions is necessary, so I feel that they should not get deleted. Also there is a high chance to lose the data created in workspace which is branched from a version to be deleted.

jimmy_chaung

How do I delete an entire branch of a revision? I came here to find out, but I think the answers went on a tangent.
Here's what I did. I saved a revision with a typo. I couldn't rename it, so I made another revision immediately after. Now, I cannot delete that one with the typo. So two issues: cannot rename revisions (found it), cannot delete branches of revision (haven't found it). I tried deleting the one without the typo also - it didn't work.

CaptainBisquick

shashank_aarya said:

@laird_broadfield Versions are always read only because they indicates the revision of document hence cannot be deleted. In any other PDM systems such as Windchill, Team center they also have same things for their revisions. e.g. Revision A is derived from initial release, Revision B is derived from revision A and so on for next revisions. In this case deleting the revision A will not make any meaning for revision B since it has reference from A. So we cannot delete any revisions. Same concept is used in Onshape as versions.

None of this makes any sense to me. How about OnShape model it's VC system on Git instead, where things are rarely lost and changes can always be deleted? Having versions sitting around that I can't delete is super irritating. What is the exact technical limitation that makes deleting of a version physically impossible? Clearly it's not impossible, because I can delete an OnShape document, which contains versions, so clearly they can be deleted. 

lobodpav

Unfortunately, it's still not possible to delete a version even after 7 years. Just created a version to realise I need to include a little change in it. I'll be having two versions now, one being totally unnecessary and confusing.

Coming from GIT, tags (i.e. versions) can be easily removed. Not sure why it's hard to do the same in Onshape.

S1mon

Versions are meant to be immutable since they can be referenced elsewhere. The one thing you can do after the fact is rename it.

One could argue that perhaps versions that aren't being used anywhere could be changed back to a micro version, but ultimately versions are free. It doesn't really hurt to have more of them.

Rhett_Robinson

Changing a version back to a micro version could come in handy, I can see it being similar to obsoleting and rereleasing. I agree that versions are free, but it would clean up the tree when I have to change the name to "V57 - Ignore" because I forgot a small update.

jeff_mcclain

What if I've made "horrible errors" on my "main" version and I want to "revert" back to a Previous Version? At this point, it appears I have to go back and make a "branch" B1 from the last known good version, then I still have a "main" listed on the bad branch…how to move "main" to the new (old) branch and continue there?

NeilCooke

https://forum.onshape.com/discussion/comment/106882#Comment_106882

No branch needed, just restore old version to main.