@himorin - FYI, I've added a rule in the deploy.yml file to allow for manually kicking off the workflow - I found out that bikeshed service returned an internal server error when the previous PR has been merged and I do not think we have a way of detecting that when using curl, so in order to re-deploy the correct version of the spec, it should now be possible to manually schedule the workflow. I have not tried to re-run an already finished workflow though, so this change may not be useful enough to adopt in the deploy.yml template that the automated scripts apply on the repositories.
@himorin - FYI, I've added a rule in the deploy.yml file to allow for manually kicking off the workflow - I found out that bikeshed service returned an internal server error when the previous PR has been merged and I do not think we have a way of detecting that when using
curl, so in order to re-deploy the correct version of the spec, it should now be possible to manually schedule the workflow. I have not tried to re-run an already finished workflow though, so this change may not be useful enough to adopt in the deploy.yml template that the automated scripts apply on the repositories.