neosourceDocs
Search docs

Update a repo label

PATCH/api/repos/{owner}/{repo}/labels/{label_id}

updateRepoLabel

Partial update: omitted fields are unchanged. A label id belonging to another repo answers 404, not 403.

Requires authentication using a bearer token or a session cookie — see tokens and scopes.

curl

curl -X PATCH 'https://neosource.dev/api/repos/OWNER/REPO/labels/LABEL_ID' \
  -H 'Authorization: Bearer $NEOSOURCE_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{}'

fetch

fetch("https://neosource.dev/api/repos/OWNER/REPO/labels/LABEL_ID", {
  method: "PATCH",
  headers: {
    Authorization: "Bearer $NEOSOURCE_TOKEN",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({}),
});

Path parameters

ownerrequired

string

reporequired

string

label_idrequired

string

Request bodyrequired

application/json

UpdateLabelRequest

object

Partial label update. Every field is optional; omitted fields are left unchanged. The label's scope (repo vs team) is not updatable.

color

string | null

description

string | null

name

string | null

Responses

200Label updated

application/json

LabelResponse

object

colorrequired

string

created_atrequired

integerint64

descriptionrequired

string

label_idrequired

string

namerequired

string

repo_id

string | null

team_id

string | null

Standard errors

Bodies documented once for the whole API — see standard errors.

  • 400Bad Request — one of: invalid_input
  • 401Authentication required
  • 403Forbidden — one of: forbidden
  • 404Not Found — one of: not_found
  • 409Conflict — one of: already_exists, conflict, non_fast_forward
  • 423Locked — one of: busy
  • 429Rate limited — retry after the `Retry-After` header
  • 500Internal server error
  • 503Service temporarily unavailable / at capacity — retry after the `Retry-After` header
  • 504Gateway timeout — the request exceeded the server's handling budget