List labels

A repository's labels, by name: each one's color (six hex digits), description, and how many issues and pull requests carry it.

GET/repos/{owner}/{name}/labels

A new repository starts with bug, documentation, duplicate, enhancement, good first issue, help wanted, invalid, question, wontfix, dependencies and security.

By name. A new repository starts with the default labels; add_default_labels adds those an older one is missing.

Authentication: Optional. Public data can be read without a token; send one to see what is private.
MCP tool: repository with action list_labels, and the same inputs
Scope: An access token needs repo:read.

Path parameters

Name	Type	Required	Description
`owner`	string	Yes	The workspace that owns the repository.
`name`	string	Yes	The repository’s name.

Example request

curl https://api.g1t.sh/repos/flagon-io/hello/labels \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

[
  {
    "name": "bug",
    "color": "d73a4a",
    "description": "Something isn't working",
    "issues": 4,
    "pulls": 1
  },
  {
    "name": "dependencies",
    "color": "0366d6",
    "description": "Updates a dependency",
    "issues": 0,
    "pulls": 6
  },
  {
    "name": "good first issue",
    "color": "7057ff",
    "description": "Good for newcomers",
    "issues": 2,
    "pulls": 0
  }
]

Errors

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.
422	`invalid`	The input is not valid. `message` says which field and why.