@@ -310,7 +310,7 @@ The following table gives an overview of how the API functions generally behave.
...
@@ -310,7 +310,7 @@ The following table gives an overview of how the API functions generally behave.
The following table shows the possible return codes for API requests.
The following table shows the possible return codes for API requests.
| Return values | Description |
| Return values | Description |
| ------------- | ----------- |
| ------------------------ | ----------- |
| `200 OK` | The `GET`, `PUT` or `DELETE` request was successful, the resource(s) itself is returned as JSON. |
| `200 OK` | The `GET`, `PUT` or `DELETE` request was successful, the resource(s) itself is returned as JSON. |
| `204 No Content` | The server has successfully fulfilled the request and that there is no additional content to send in the response payload body. |
| `204 No Content` | The server has successfully fulfilled the request and that there is no additional content to send in the response payload body. |
| `201 Created` | The `POST` request was successful and the resource is returned as JSON. |
| `201 Created` | The `POST` request was successful and the resource is returned as JSON. |
...
@@ -323,7 +323,8 @@ The following table shows the possible return codes for API requests.
...
@@ -323,7 +323,8 @@ The following table shows the possible return codes for API requests.
| `409 Conflict` | A conflicting resource already exists, e.g., creating a project with a name that already exists. |
| `409 Conflict` | A conflicting resource already exists, e.g., creating a project with a name that already exists. |
| `412` | Indicates the request was denied. May happen if the `If-Unmodified-Since` header is provided when trying to delete a resource, which was modified in between. |
| `412` | Indicates the request was denied. May happen if the `If-Unmodified-Since` header is provided when trying to delete a resource, which was modified in between. |
| `422 Unprocessable` | The entity could not be processed. |
| `422 Unprocessable` | The entity could not be processed. |
| `500 Server Error` | While handling the request something went wrong server-side. |
| `429 Too Many Requests` | The user exceeded the [application rate limits](../administration/instance_limits.md#rate-limits). |
| `500 Server Error` | While handling the request, something went wrong server-side. |
@@ -434,5 +434,8 @@ npm dist-tag rm @scope/package@version my-tag # Delete a tag from the package
...
@@ -434,5 +434,8 @@ npm dist-tag rm @scope/package@version my-tag # Delete a tag from the package
npm install @scope/package@my-tag # Install a specific tag
npm install @scope/package@my-tag # Install a specific tag
```
```
NOTE: **Note:**
You cannot use your `CI_JOB_TOKEN` or deploy token with the `npm dist-tag` commands. View [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/258835) for details.
CAUTION: **Warning:**
CAUTION: **Warning:**
Due to a bug in NPM 6.9.0, deleting dist tags fails. Make sure your NPM version is greater than 6.9.1.
Due to a bug in NPM 6.9.0, deleting dist tags fails. Make sure your NPM version is greater than 6.9.1.
@@ -79,6 +79,9 @@ This will enable the `Bug` dropdown option when creating or editing issues. When
...
@@ -79,6 +79,9 @@ This will enable the `Bug` dropdown option when creating or editing issues. When
to the issue description field. The 'Reset template' button will discard any
to the issue description field. The 'Reset template' button will discard any
changes you made after picking the template and return it to its initial status.
changes you made after picking the template and return it to its initial status.
TIP: **Tip:**
You can create short-cut links to create an issue using a designated template. For example: `https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Feature%20proposal`.
@@ -8,8 +8,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
...
@@ -8,8 +8,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5554) in [GitLab 8.11](https://about.gitlab.com/releases/2016/08/22/gitlab-8-11-released/#issue-board).
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5554) in [GitLab 8.11](https://about.gitlab.com/releases/2016/08/22/gitlab-8-11-released/#issue-board).
## Overview
The GitLab Issue Board is a software project management tool used to plan,
The GitLab Issue Board is a software project management tool used to plan,
organize, and visualize a workflow for a feature or product release.
organize, and visualize a workflow for a feature or product release.
It can be used as a [Kanban](https://en.wikipedia.org/wiki/Kanban_(development)) or a
It can be used as a [Kanban](https://en.wikipedia.org/wiki/Kanban_(development)) or a
it'proxies wiki commit to primary node and ultmately replicates to secondary node',testcase: 'https://gitlab.com/gitlab-org/quality/testcases/-/issues/694'do
it'proxies wiki commit to primary node and ultmately replicates to secondary node',testcase: 'https://gitlab.com/gitlab-org/quality/testcases/-/issues/694'do
QA::Runtime::Logger.debug('*****Visiting the secondary geo node*****')
QA::Runtime::Logger.debug('*****Visiting the secondary geo node*****')