phab should show a warning and ask the user for confirmation if the target repository contains new commits added since a previous artifact deployment. If the user confirms the deployment process continues as usual, if the user declines, the deployment process is aborted.
When running the deployment with --no-interaction phab will throw an exception. This can be prevented via the --force flag (same as the current behavior).
@d34dman what do you think? should be a good compromise, keeping the target repo sane and prevents accidental overrides. Devs get a notifcation that sth did not work as expected and can react accordingly (e.g. check the situation, run the deployment manually)
phab should show a warning and ask the user for confirmation if the target repository contains new commits added since a previous artifact deployment. If the user confirms the deployment process continues as usual, if the user declines, the deployment process is aborted.
When running the deployment with
--no-interactionphab will throw an exception. This can be prevented via the--forceflag (same as the current behavior).@d34dman what do you think? should be a good compromise, keeping the target repo sane and prevents accidental overrides. Devs get a notifcation that sth did not work as expected and can react accordingly (e.g. check the situation, run the deployment manually)