ci: require run-e2e label for automatic GitLab E2E - #158
Merged
Merged
Conversation
fengmk2
changed the title
fengmk2
added
the
run-e2e
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
GitLab CI has limited capacity. Automatic GitLab E2E runs now require a maintainer to add
run-e2eto a PR. This applies to PRs from this repository and forks. Each new commit requires a new label event.The workflow checks the maintainer's access, the current PR commit, and the label before it starts the full suite. Pushes, merge queues, and release tags no longer start GitLab pipelines.
workflow_dispatchremains available with its existing inputs and defaults.