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
Currently the webhook seems to handle either push or pipeline/workflow run events and it already captures the status of the workflow run. But it doesn't seem to use this value as far as I can see. So currently if your puppet-control repo has a test workflow in GitHub then the webhook will get triggered 3 times (requested, in_progress and completed). But ideally it would ignore the first two and only deploy the environment/module if the workflow succeeds. Thus ensuring only environments/modules passing CI would get deployed.
The text was updated successfully, but these errors were encountered:
Currently the webhook seems to handle either push or pipeline/workflow run events and it already captures the status of the workflow run. But it doesn't seem to use this value as far as I can see. So currently if your
puppet-control
repo has a test workflow in GitHub then the webhook will get triggered 3 times (requested
,in_progress
andcompleted
). But ideally it would ignore the first two and only deploy the environment/module if the workflow succeeds. Thus ensuring only environments/modules passing CI would get deployed.The text was updated successfully, but these errors were encountered: