Run stepup-behat tests only once #73
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prior to this change, the stepup-behat tests would almost always run twice on every commit: one for 'push' and one for 'pull_request'. This change only runs the 'push' run on the main branch. This means, if there is no PR, it will also not run the tests on other branches. `workflow_dispatch` adds the option to start the pipeline manually. Running the tests twice caused issues with cdns (npm, composer) on other projects.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior to this change, the stepup-behat tests would almost always run twice on every commit: one for 'push' and one for 'pull_request'.
This change only runs the 'push' run on the main branch.
This means, if there is no PR, it will also not run the tests on other branches.
workflow_dispatchadds the option to start the pipeline manually.Running the tests twice caused issues with cdns (npm, composer) on other projects.