engine: use API definitions from default branch #16459
Merged
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
The default branch has separate files for each API version, so we can consume the swagger files from that branch (we only publish the ones that have been released through the stubs in the engine/api/ directory). Using the default (master) branch allows for API docs changes to be published without them being cherry-picked into the release branch. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
thaJeztah
added
area/engine
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
crazy-max
approved these changes
Jan 7, 2023
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.
The default branch has separate files for each API version, so we can consume the swagger files from that branch (we only publish the ones that have been released through the stubs in the engine/api/ directory). Using the default (master) branch allows for API docs changes to be published without them being cherry-picked into the release branch.