Repository navigation
Ignore the CLA check when labeling dependency PRs - #2453
Draft
mbiernacik wants to merge 1 commit into
Draft
mbiernacik wants to merge 1 commit into
mbiernacik wants to merge 1 commit into
Conversation
Collaborator
apilaskowski
marked this pull request as draft
November 18, 2026 10:13
This branch has not been deployed
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
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.
The CLA check fails for commits of bot accounts that aren't covered by a CLA, e.g. the dataform-security-updates GitHub App, so dependency PRs whose tests only wait for new versions in CI were treated as real failures and not labeled. Ignore checks that say nothing about the code.