---
title: "Rename, recolour or describe a label (owners); a rename moves it on every issue in one step"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.gitpando.com/llms.txt
> Use this file to discover all available pages before exploring further.

Path: Pando API › issues

`PATCH /v1/monorepos/{owner}/{monorepo}/labels/{label}`

## Authentication

Requires one of the following:

- `credential`, http, header `Authorization`
- `session`, apiKey, in cookie

## Path parameters

- `updateLabel.path.owner` (string, required) — The monorepo's owner, a namespace (a person's login or an organization). Matched without case.
  - pattern `^[a-z0-9](?:[a-z0-9]|-(?=[a-z0-9])){0,38}$`
- `updateLabel.path.monorepo` (string, required) — The monorepo's name within its owner (or an old name). Matched without case.
  - pattern `^[a-z0-9](?:[a-z0-9._]|-(?!-)){0,38}$`
- `updateLabel.path.label` (string, required)

## Request body

_Required._

- `updateLabel.name` (string, optional)
  - minLength 1; maxLength 50
- `updateLabel.color` (string, optional) — Each theme sets the eight from its own tokens (no red, so a label never reads as a failure).
  - one of `"gray"`, `"orange"`, `"yellow"`, `"green"`, `"teal"`, `"blue"`, `"purple"`, `"pink"`
- `updateLabel.description` (string | null, optional)
  - maxLength 100

## Example request

```json
{
  "name": "string",
  "color": "gray",
  "description": "string"
}
```

## Code samples

### cURL

```curl
curl --request PATCH \
  --url https://app.gitpando.com/v1/monorepos/string/string/labels/string \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "string",
  "color": "gray",
  "description": "string"
}
'
```

### TypeScript

```typescript
const url = 'https://app.gitpando.com/v1/monorepos/string/string/labels/string';
const options = {
  method: 'PATCH',
  headers: {'Content-Type': 'application/json', Authorization: 'Bearer <token>'},
  body: JSON.stringify({name: 'string', color: 'gray', description: 'string'})
};

fetch(url, options)
  .then(res => res.json())
  .then(json => console.log(json))
  .catch(err => console.error(err));
```

### Python

```python
import requests

url = "https://app.gitpando.com/v1/monorepos/string/string/labels/string"

payload = {
    "name": "string",
    "color": "gray",
    "description": "string"
}
headers = {
    "Content-Type": "application/json",
    "Authorization": "Bearer <token>"
}

response = requests.patch(url, json=payload, headers=headers)

print(response.text)
```

## Responses

### 200

The label now.

#### Example

```json
{
  "name": "string",
  "color": "gray",
  "description": "string"
}
```

- `updateLabel.response.200.name` (string, required) — 1 to 50 characters, unique ignoring case.
- `updateLabel.response.200.color` (string, required) — Each theme sets the eight from its own tokens (no red, so a label never reads as a failure).
  - one of `"gray"`, `"orange"`, `"yellow"`, `"green"`, `"teal"`, `"blue"`, `"purple"`, `"pink"`
- `updateLabel.response.200.description` (string | null, required)

### 403

An error

#### Example

```json
{
  "error": {
    "code": "string",
    "message": "string",
    "paths": [
      "string"
    ],
    "checks": {
      "sha": "string",
      "state": "success",
      "required": [
        "string"
      ],
      "checks_unknown": "string",
      "missing": [
        "string"
      ],
      "statuses": [
        {
          "sha": "string",
          "context": "string",
          "state": "pending",
          "target_url": "string",
          "description": "string",
          "creator": "string",
          "app": "string",
          "created_at": "2019-08-24T14:15:22Z"
        }
      ]
    }
  }
}
```

- `updateLabel.response.403.error` (object, required)
  - `updateLabel.response.403.error.code` (string, required)
  - `updateLabel.response.403.error.message` (string, required)
  - `updateLabel.response.403.error.paths` (array<string>, optional)
  - `updateLabel.response.403.error.checks` (object, optional) — GitHub's combined status, plus the required contexts and which are missing.
    - `updateLabel.response.403.error.checks.sha` (string | null, required)
    - `updateLabel.response.403.error.checks.state` (string, required) — `success` when the merge gate passes; `missing` when a required context has not reported; `unknown` while the required checks are (an unforced merge is refused).
      - one of `"success"`, `"pending"`, `"failure"`, `"error"`, `"missing"`, `"unknown"`
    - `updateLabel.response.403.error.checks.required` (array | null, required) — Null while unknown.
    - `updateLabel.response.403.error.checks.checks_unknown` (string | null, required) — Why the required checks are unknown, in plain words: "Pando couldn't read this monorepo's required checks; try again", or "pando.toml line 3: expected comma or end of structure; fix it on main, or merge with force". Null otherwise.
    - `updateLabel.response.403.error.checks.statuses` (array<object>, required) — The latest status per context.
      - `updateLabel.response.403.error.checks.statuses.sha` (string, required)
      - `updateLabel.response.403.error.checks.statuses.context` (string, required)
      - `updateLabel.response.403.error.checks.statuses.state` (string, required)
        - one of `"pending"`, `"success"`, `"failure"`, `"error"`
      - `updateLabel.response.403.error.checks.statuses.created_at` (string, required)
        - format `date-time`
      - `updateLabel.response.403.error.checks.statuses.target_url` (string | null, optional)
      - `updateLabel.response.403.error.checks.statuses.description` (string | null, optional)
      - `updateLabel.response.403.error.checks.statuses.creator` (string, optional) — The member who posted it (a login); `app:<slug>` for a status posted with a status token or by a CI integration; `hook:<hook id>` for a status token from a web hook with no app.
      - `updateLabel.response.403.error.checks.statuses.app` (string | null, optional) — The CI service that reported it (`buildkite`, `github-actions`, ...), stamped by Pando from a status token or a CI integration, never from the body or `target_url`. Null when a member posted it with their own credential. The web shows the service's mark for a slug it knows.
    - `updateLabel.response.403.error.checks.missing` (array<string>, optional)

### 404

An error

#### Example

```json
{
  "error": {
    "code": "string",
    "message": "string",
    "paths": [
      "string"
    ],
    "checks": {
      "sha": "string",
      "state": "success",
      "required": [
        "string"
      ],
      "checks_unknown": "string",
      "missing": [
        "string"
      ],
      "statuses": [
        {
          "sha": "string",
          "context": "string",
          "state": "pending",
          "target_url": "string",
          "description": "string",
          "creator": "string",
          "app": "string",
          "created_at": "2019-08-24T14:15:22Z"
        }
      ]
    }
  }
}
```

- `updateLabel.response.404.error` (object, required)
  - `updateLabel.response.404.error.code` (string, required)
  - `updateLabel.response.404.error.message` (string, required)
  - `updateLabel.response.404.error.paths` (array<string>, optional)
  - `updateLabel.response.404.error.checks` (object, optional) — GitHub's combined status, plus the required contexts and which are missing.
    - `updateLabel.response.404.error.checks.sha` (string | null, required)
    - `updateLabel.response.404.error.checks.state` (string, required) — `success` when the merge gate passes; `missing` when a required context has not reported; `unknown` while the required checks are (an unforced merge is refused).
      - one of `"success"`, `"pending"`, `"failure"`, `"error"`, `"missing"`, `"unknown"`
    - `updateLabel.response.404.error.checks.required` (array | null, required) — Null while unknown.
    - `updateLabel.response.404.error.checks.checks_unknown` (string | null, required) — Why the required checks are unknown, in plain words: "Pando couldn't read this monorepo's required checks; try again", or "pando.toml line 3: expected comma or end of structure; fix it on main, or merge with force". Null otherwise.
    - `updateLabel.response.404.error.checks.statuses` (array<object>, required) — The latest status per context.
      - `updateLabel.response.404.error.checks.statuses.sha` (string, required)
      - `updateLabel.response.404.error.checks.statuses.context` (string, required)
      - `updateLabel.response.404.error.checks.statuses.state` (string, required)
        - one of `"pending"`, `"success"`, `"failure"`, `"error"`
      - `updateLabel.response.404.error.checks.statuses.created_at` (string, required)
        - format `date-time`
      - `updateLabel.response.404.error.checks.statuses.target_url` (string | null, optional)
      - `updateLabel.response.404.error.checks.statuses.description` (string | null, optional)
      - `updateLabel.response.404.error.checks.statuses.creator` (string, optional) — The member who posted it (a login); `app:<slug>` for a status posted with a status token or by a CI integration; `hook:<hook id>` for a status token from a web hook with no app.
      - `updateLabel.response.404.error.checks.statuses.app` (string | null, optional) — The CI service that reported it (`buildkite`, `github-actions`, ...), stamped by Pando from a status token or a CI integration, never from the body or `target_url`. Null when a member posted it with their own credential. The web shows the service's mark for a slug it knows.
    - `updateLabel.response.404.error.checks.missing` (array<string>, optional)


Source: https://docs.gitpando.com/api/issues/updateLabel/index.md
