Update Repository
Since this endpoint can be used to both update and to create a repository, the request body depends on the intent.
Creation
See the POST documentation for the repository endpoint for an example of the request body.
Update
Note: Changing the name
of the repository will cause the location to be changed. This is because the URL of the repo is derived from the name (a process called slugification). In such a scenario, it is possible for the request to fail if the newly created slug conflicts with an existing repository’s slug. But if there is no conflict, the new location will be returned in the Location
header of the response.
To learn more, visit the Bitbucket documentation.
Parameters
Parameter | Description |
---|---|
Default Branch | A ref object, representing a branch or tag in a repository. |
Description | - |
Fork Policy | Controls the rules for forking this repository.- allow_forks: unrestricted forking |
- nopublicforks: restrict forking to private forks (forks cannotbe made public later)
- no_forks: deny all forking. |
| Has Issues | - |
| Has Wiki | - |
| Is Private | - |
| Language | - |
| Project | A Bitbucket project.Projects are used by teams to organize repositories. |
| Repo Slug | This can either be the repository slug or the UUID of the repository,surrounded by curly-braces, for example:
{repository UUID}
. | | Repo name | - | | Workspace Slug | This can either be the workspace ID (slug) or the workspace UUIDsurrounded by curly-braces, for example:{workspace UUID}
. |
Example Output
Workflow Library Example
Update Repository with Bitbucket and Send Results Via Email
Preview this Workflow on desktop
Was this page helpful?