You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the following command, the mass-update plugin executes as intended, and works well. terminus site:list --format=list | terminus site:mass-update:apply
But upon attempting to apply an update where the site has a merge conflict present, the script terminates upon receiving that error.
Potential solutions
Allow script to continue executing the remaining items in the queue. Either by default or via another option within the plugin.
Allow for the --dry-run option to test for merge conflicts prior to actually executing the script ahead of time.
Thanks for all that you do! :-)
The text was updated successfully, but these errors were encountered:
Good ideas, @SteveRyan-ASU. Testing for merge conflicts conflicts doesn't seem as useful to me as something like a --continue-on-failure flag, and possible spitting out which sites errored at the end.
Agreed about the approach as well. That would also allow the script to continue if it encountered other errors along the way as well. Example: trying to mass-update update a site that was still in SFTP mode would probably also result in the script stopping execution. (Untested.)
When running the following command, the mass-update plugin executes as intended, and works well.
terminus site:list --format=list | terminus site:mass-update:apply
But upon attempting to apply an update where the site has a merge conflict present, the script terminates upon receiving that error.
Potential solutions
--dry-run
option to test for merge conflicts prior to actually executing the script ahead of time.Thanks for all that you do! :-)
The text was updated successfully, but these errors were encountered: