chore: drop vestigial enableFullYaml field from Build type - #9
Merged
Conversation
The backend no longer emits enableFullYaml in its API responses (the YAML-migration flag has been removed as dead code), and nothing in the CLI ever read this hand-written optional. Remove it. The orval-generated types never carried this field, so no regeneration is needed.
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.
Companion to GoodRxOSS/lifecycle#228 (dead-code cleanup phase 1). The backend no longer emits
enableFullYamlin its API responses, and nothing in the CLI ever read this hand-written optionalBuildtype field. The orval-generated types never carried it, so no regeneration is needed.webhooksYamlis left in place — the backendbuilds.webhooksYamlfield is still live.