Closed thumDer closed 4 years ago
Fixed and will be published with next release
Only one comment on this: the first run of update still breaks the currently deployed clone, so it needs to be cloned again, but after that it seems to perform the update. Is there any way to only execute the update if the current clone is not up-to-date?
Yeah I'm doing another round of fixes on the update mechanism
Thx! In the meanwhile I'm handling it in the PowerShell script to check the clones version number.
Describe the bug When I try to update a clone (base deployment) it fails, pyrevit forgets the clone and also removes it from the config.ini.
To Reproduce
Expected behavior It should update the clone if possible, or report if it is up to date.
Desktop (please complete the following information):
Additional context
The complete process from powershell: