Skip to content

Change an issue's title, body, labels or the people it is assigned to.

PATCH/repos/{owner}/{name}/issues/{number}

Only the fields given are changed; labels and assignees each replace the whole set. Its author may change their own issue; anyone else needs the Triage role or higher.

Name Type Required Description
owner string Yes The workspace that owns the repository.
name string Yes The repository’s name.
number integer Yes The number shown after the #. Issues and pull requests share one sequence.

Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.

Name Type Required Description
title string No
body string No
labels array of strings No
assignees array of strings No Usernames of the people it is assigned to. Replaces the whole set; an empty list unassigns everyone. To assign it to the g1t agent, use assign_issue.
curl -X PATCH https://api.g1t.sh/repos/flagon-io/hello/issues/12 \
-H "Authorization: Bearer $G1T_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"labels": [
"feature",
"good first issue"
],
"assignees": [
"syntaqx"
]
}'

A successful request answers 200 with:

{
"id": "iss_01m43shrzpfe49x74ga7sj1c6v",
"repo_id": "rep_01m3m5q6p0e2qaw6mmjahk0qrr",
"number": 12,
"title": "Greeting should name the caller",
"body": "Take a name from the first argument; fall back to world.",
"labels": [
"feature",
"good first issue"
],
"checks": [
"cargo test"
],
"state": "open",
"reason": null,
"resolved_by": null,
"author": {
"id": "usr_01kkntcg1eeb98j62xjm7eh09p",
"username": "syntaqx",
"kind": "user",
"verified": false,
"workspaces": []
},
"created_at": "2026-10-01T18:04:11.482Z",
"updated_at": "2026-10-01T18:09:47.305Z",
"closed_at": null,
"pull_count": 0,
"comment_count": 0,
"assignees": [
"syntaqx"
],
"blocked_by": [],
"queued": false,
"agent": null
}

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status Code When
401 unauthenticated A token is required, or the one sent is not valid.
403 forbidden The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404 not_found It does not exist, or you cannot see it.
409 conflict The request conflicts with the current state.
422 invalid The input is not valid. message says which field and why.