Create a branch
Create a new branch, or rename and confirm the default branch.
Headers
API contract version. Defaults to the oldest supported version.
API contract version. Defaults to the oldest supported version.
Target project ID when no project ID is present in the path. Project API keys default to their bound project. If supplied, the header must match both the path target and the key’s bound project.
Target project ID when no project ID is present in the path. Project API keys default to their bound project. If supplied, the header must match both the path target and the key’s bound project.
Request body
Response
Created or existing branch
Changes
Changed in 3 of the 15 revisions of this API.118
- ○
the endpoint scheme security
UserBearerAuthwas removed from the APIapi-security-removed
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ○
the endpoint scheme security
UserBearerAuthwas added to the APIapi-security-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ▲
removed the media type
text/plainfor the response with the statusresponse-media-type-removed
- ○
the endpoint scheme security
BearerAuthwas added to the APIapi-security-added
- ○
api tag
Projectaddedapi-tag-added
- ○
api tag
Branchesremovedapi-tag-removed
- ○
added the media type
application/jsonfor the response with the statusresponse-media-type-added
- ○
added the media type
text/htmlfor the response with the statusresponse-media-type-added
- ○
added the media type
text/htmlfor the response with the statusresponse-media-type-added
- ○
added the media type
text/htmlfor the response with the statusresponse-media-type-added
- ○
added the non-success response with the status
response-non-success-status-added
- ○
added the non-success response with the status
response-non-success-status-added
- ○
added the non-success response with the status
response-non-success-status-added
- ○
added the non-success response with the status
response-non-success-status-added
- ○
the response property
became required for the statusresponse-property-became-required
- ○
the response property
/became required for the statusresponse-property-became-required
- ○
the response property
/became required for the statusresponse-property-became-required
- ○
the response property
became required for the statusresponse-property-became-required
- ○
the response property
became required for the statusresponse-property-became-required
This revision also has 5 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲