Skip GitLab pipelines for GitHub merge queue#11314
Open
sarahchen6 wants to merge 1 commit intomasterfrom
Open
Conversation
sarahchen6
added
tag: no release notes
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
2 participants
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.
What Does This Do
Skip running GitLab pipelines for PRs on the GitHub merge queue
Motivation
Our current use of GitHub merge queues is that they direct PRs to the Datadog queue. However during this redirection process, a GitLab GH MQ pipeline for the PR is still created. We don't actually need this pipeline since we use the Datadog queue, so this PR should auto-cancel pipelines coming from the GH MQ. Example pipeline: https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-java/-/pipelines/112036798
Additional Notes
We can test this by merging this PR via the GH MQ and checking its associated GitLab pipeline.
Contributor Checklist
type:and (comp:orinst:) labels in addition to any other useful labelsclose,fix, or any linking keywords when referencing an issueUse
solvesinstead, and assign the PR milestone to the issueJira ticket: [PROJ-IDENT]
Note: Once your PR is ready to merge, add it to the merge queue by commenting
/merge./merge -ccancels the queue request./merge -f --reason "reason"skips all merge queue checks; please use this judiciously, as some checks do not run at the PR-level. For more information, see this doc.