[PP-7833] Disable GraphQL precedence tests#4117
Merged
Merged
Conversation
852f684 to
3fe6995
Compare
AgaDufrat
previously approved these changes
Jul 7, 2026
AgaDufrat
left a comment
Contributor
There was a problem hiding this comment.
LGTM.
I'd probably just remove them instead of leaving a long comment. We can always revert the commit and update the setup, if things change.
3fe6995 to
31d7bc9
Compare
Per the comment, we're removing these from the CI workflow for now given our GraphQL functionality is not in active development and they are therefore wasting resources. This adds a check against GraphQL and link expansion files to remind us to re-enable them if we work on code that these tests are likely to exercise. This change can be reverted when that is the case
31d7bc9 to
6090f1b
Compare
Member
Author
Much cleaner! |
AgaDufrat
approved these changes
Jul 7, 2026
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.
Per the comments, we're disabling these for now given our GraphQL functionality is not in active development and they are therefore wasting CI resources. This adds a check against GraphQL and link expansion files to remind us to re-enable them if we work on code that these tests are likely to exercise. This change can be reverted when that is the case