Skip to content

engine: use API definitions from default branch #16459

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thaJeztah merged 1 commit into from
Jan 7, 2023
Merged

engine: use API definitions from default branch #16459

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion _config.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -171,7 +171,12 @@ fetch-remote:

- repo: "https://github.com/docker/docker"
default_branch: "master"
ref: "20.10"
# 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.
ref: "master"
paths:
- dest: "engine/api"
src:
Expand Down