-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to use Waves #489
Comments
any update? We are currently using the suggested hack: const options: AddGitHubStageOptions = {
jobSettings: {
if: `always() &&\n!contains(needs.*.result, 'failure') &&\n!contains(needs.*.result, 'cancelled') &&\ngithub.ref_name == ${env.branch}`,
},
} to decouple dependency between stages, but it would be nicer to use a wave |
Progress is being made on the PR #490 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a paired-down version of #376
Would like the ability to use Waves, as in the following modified test case:
Currently we lose the ability to use
GitHubActionStep
inpre
andpost
as well as anyAddGitHubStageOptions
values not inherited fromStageProps
.The text was updated successfully, but these errors were encountered: