@@ -1467,8 +1467,10 @@ After creating and configuring Gitaly Cluster:
1.[Schedule repository storage moves for all projects on a storage shard](../../api/project_repository_storage_moves.md#schedule-repository-storage-moves-for-all-projects-on-a-storage-shard) using the API. For example:
```shell
curl --request POST --header"Private-Token: <your_access_token>"--header"Content-Type: application/json"\
1.[Query the most recent repository moves](../../api/project_repository_storage_moves.md#retrieve-all-project-repository-storage-moves)
...
...
@@ -1500,8 +1502,10 @@ After creating and configuring Gitaly Cluster:
1.[Schedule repository storage moves for all snippets on a storage shard](../../api/snippet_repository_storage_moves.md#schedule-repository-storage-moves-for-all-snippets-on-a-storage-shard) using the API. For example:
```shell
curl --request POST --header"PRIVATE-TOKEN: <your_access_token>"--header"Content-Type: application/json"\
1.[Query the most recent repository moves](../../api/snippet_repository_storage_moves.md#retrieve-all-snippet-repository-storage-moves)
...
...
@@ -1525,8 +1529,10 @@ After creating and configuring Gitaly Cluster:
1.[Schedule repository storage moves for all groups on a storage shard](../../api/group_repository_storage_moves.md#schedule-repository-storage-moves-for-all-groups-on-a-storage-shard) using the API.
```shell
curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" --header "Content-Type: application/json" \
curl --request POST --header"PRIVATE-TOKEN: <your_access_token>"--data"name=MyApplication&redirect_uri=http://redirect.uri&scopes=""https://gitlab.example.com/api/v4/applications"
curl --request POST --header"PRIVATE-TOKEN: <your_access_token>"\
curl --data"message=Deploy in progress&color=#cecece"--header"PRIVATE-TOKEN: <your_access_token>""https://gitlab.example.com/api/v4/broadcast_messages"
curl --data"message=Deploy in progress&color=#cecece"\
| `message` | string | no | A custom commit message to use for the new commit. [Introduced in GitLab 14.0](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/62481)
```shell
curl --request POST --header"PRIVATE-TOKEN: <your_access_token>"--form"branch=master""https://gitlab.example.com/api/v4/projects/5/repository/commits/master/cherry_pick"
curl --request POST --header"PRIVATE-TOKEN: <your_access_token>"\
| `dry_run` | boolean | no | Does not commit any changes. Default is false. [Introduced in GitLab 13.3](https://gitlab.com/gitlab-org/gitlab/-/issues/231032) |
```shell
curl --request POST --header"PRIVATE-TOKEN: <your_access_token>"--form"branch=master""https://gitlab.example.com/api/v4/projects/5/repository/commits/a738f717824ff53aebad8b090c1b79a14f2bd9e8/revert"
curl --request POST --header"PRIVATE-TOKEN: <your_access_token>"--form"branch=master"\
@@ -90,7 +90,8 @@ GET /groups/:id/registry/repositories
| `tags_count` | boolean | no | If the parameter is included as true, each repository includes `"tags_count"` in the response ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/32141) in GitLab 13.1). |
@@ -90,7 +90,8 @@ PUT /projects/:id/custom_attributes/:key
| `value` | string | yes | The value of the custom attribute |
```shell
curl --request PUT --header"PRIVATE-TOKEN: <your_access_token>"--data"value=Greenland""https://gitlab.example.com/api/v4/users/42/custom_attributes/location"
curl --request PUT --header"PRIVATE-TOKEN: <your_access_token>"\
@@ -197,7 +198,8 @@ PUT /projects/:id/environments/:environments_id
| `external_url` | string | no | The new `external_url` |
```shell
curl --request PUT --data"name=staging&external_url=https://staging.gitlab.example.com"--header"PRIVATE-TOKEN: <your_access_token>""https://gitlab.example.com/api/v4/projects/1/environments/1"
curl --request PUT --data"name=staging&external_url=https://staging.gitlab.example.com"\
| `image_url` | string | yes | URL of the badge image |
```shell
curl --request POST --header"PRIVATE-TOKEN: <your_access_token>"--data"link_url=https://gitlab.com/gitlab-org/gitlab-foss/commits/master&image_url=https://shields.io/my/badge1&position=0""https://gitlab.example.com/api/v4/groups/:id/badges"
curl --request POST --header"PRIVATE-TOKEN: <your_access_token>"\
@@ -90,7 +91,9 @@ The `file=` parameter must point to a file on your file system and be preceded
by `@`. For example:
```shell
curl --request POST --header"PRIVATE-TOKEN: <your_access_token>"--form"name=imported-group"--form"path=imported-group"--form"file=@/path/to/file""https://gitlab.example.com/api/v4/groups/import"
curl --request POST --header"PRIVATE-TOKEN: <your_access_token>"\
| `environment_scope`**(PREMIUM)** | string | no | The [environment scope](../ci/variables/README.md#limit-the-environment-scope-of-a-cicd-variable) of a variable |
```shell
curl --request POST --header"PRIVATE-TOKEN: <your_access_token>""https://gitlab.example.com/api/v4/groups/1/variables"--form"key=NEW_VARIABLE"--form"value=new value"
curl --request POST --header"PRIVATE-TOKEN: <your_access_token>"\
@@ -125,7 +126,8 @@ PUT /groups/:id/variables/:key
| `environment_scope`**(PREMIUM)** | string | no | The [environment scope](../ci/variables/README.md#limit-the-environment-scope-of-a-cicd-variable) of a variable |
```shell
curl --request PUT --header"PRIVATE-TOKEN: <your_access_token>""https://gitlab.example.com/api/v4/groups/1/variables/NEW_VARIABLE"--form"value=updated value"
curl --request PUT --header"PRIVATE-TOKEN: <your_access_token>"\