chore: specify paths on push for e2e tests #287
Merged
Conversation
This file contains 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
📊 Package size report
|
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.
📜 Description
Specify
pathsonpushfore2etests.💡 Motivation and Context
Without these paths we'll run e2e every time on push to main branch. It's not consistent behavior across other CI scripts (and actually there is no sense not to run e2e pipeline on pull_request and run it on push).
So in this PR I'm adding these paths to have a consistent behavior across all CI scripts.
📢 Changelog
CI
pathson push for e2e tests (the same as on pull_request);🤔 How Has This Been Tested?
There is no way to test it 😅
📝 Checklist