skip yaml tests that require feature flags #1531
Merged
+13
−4
Conversation
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
picandocodigo
approved these changes
Feb 11, 2026
github-actions bot
pushed a commit
that referenced
this pull request
Feb 11, 2026
(cherry picked from commit 10e285a)
miguelgrinberg
added a commit
that referenced
this pull request
Feb 11, 2026
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.
This change adds a
$featureFlagsoption to theBuildPHPUnitClass, so that we can specify which feature flags are enabled in the server. This is used to filter out tests that require feature flags that are not enabled.The default test runner for our CI indicates that no feature flags are enabled, to prevent errors when calling endpoints that are not generated in the client.