engine: use API definitions from default branch

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>
This commit is contained in:
Sebastiaan van Stijn 2023-01-06 22:15:10 +01:00
parent 380bf39b94
commit f034af363c
No known key found for this signature in database
GPG Key ID: 76698F39D527CE8C
1 changed files with 6 additions and 1 deletions

View File

@ -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: