RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.github.com/en/rest/orgs/issue-types below:

REST API endpoints for issue types

Use the REST API to interact with issue types in an organization.

List issue types for an organization Code samples for "List issue types for an organization" Request example

get/orgs/{org}/issue-types

Copy to clipboard curl request example

curl -L \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2022-11-28" \ https://api.github.com/orgs/ORG/issue-types

Response

Status: 200

[ { "id": 410, "node_id": "IT_kwDNAd3NAZo", "name": "Task", "description": "A specific piece of work", "created_at": "2024-12-11T14:39:09Z", "updated_at": "2024-12-11T14:39:09Z" }, { "id": 411, "node_id": "IT_kwDNAd3NAZs", "name": "Bug", "description": "An unexpected problem or behavior", "created_at": "2024-12-11T14:39:09Z", "updated_at": "2024-12-11T14:39:09Z" } ]

Create issue type for an organization

Create a new issue type for an organization.

You can find out more about issue types in Managing issue types in an organization.

To use this endpoint, the authenticated user must be an administrator for the organization. OAuth app tokens and personal access tokens (classic) need the admin:org scope to use this endpoint.

Fine-grained access tokens for "Create issue type for an organization"

This endpoint works with the following fine-grained token types:

The fine-grained token must have the following permission set:

"Issue Types" organization permissions (write)

Parameters for "Create issue type for an organization" Headers Name, Type, Description

accept string

Setting to application/vnd.github+json is recommended.

Path parameters Name, Type, Description

org string Required

The organization name. The name is not case sensitive.

Body parameters Name, Type, Description

name string Required

Name of the issue type.

is_enabled boolean Required

Whether or not the issue type is enabled at the organization level.

description string or null

Description of the issue type.

color string or null

Color for the issue type.

Can be one of: gray, blue, green, yellow, orange, red, pink, purple, null

HTTP response status codes for "Create issue type for an organization" Status code Description 200

404

Resource not found

422

Validation failed, or the endpoint has been spammed.

Code samples for "Create issue type for an organization" Request example

post/orgs/{org}/issue-types

Copy to clipboard curl request example

curl -L \ -X POST \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2022-11-28" \ https://api.github.com/orgs/ORG/issue-types \ -d '{"name":"Epic","description":"An issue type for a multi-week tracking of work","is_enabled":true,"color":"green"}'

Response

Status: 200

{ "id": 410, "node_id": "IT_kwDNAd3NAZo", "name": "Task", "description": "A specific piece of work", "created_at": "2024-12-11T14:39:09Z", "updated_at": "2024-12-11T14:39:09Z" }

Update issue type for an organization

Updates an issue type for an organization.

You can find out more about issue types in Managing issue types in an organization.

To use this endpoint, the authenticated user must be an administrator for the organization. OAuth app tokens and personal access tokens (classic) need the admin:org scope to use this endpoint.

Fine-grained access tokens for "Update issue type for an organization"

This endpoint works with the following fine-grained token types:

The fine-grained token must have the following permission set:

"Issue Types" organization permissions (write)

Parameters for "Update issue type for an organization" Headers Name, Type, Description

accept string

Setting to application/vnd.github+json is recommended.

Path parameters Name, Type, Description

org string Required

The organization name. The name is not case sensitive.

issue_type_id integer Required

The unique identifier of the issue type.

Body parameters Name, Type, Description

name string Required

Name of the issue type.

is_enabled boolean Required

Whether or not the issue type is enabled at the organization level.

description string or null

Description of the issue type.

color string or null

Color for the issue type.

Can be one of: gray, blue, green, yellow, orange, red, pink, purple, null

HTTP response status codes for "Update issue type for an organization" Status code Description 200

404

Resource not found

422

Validation failed, or the endpoint has been spammed.

Code samples for "Update issue type for an organization" Request example

put/orgs/{org}/issue-types/{issue_type_id}

Copy to clipboard curl request example

curl -L \ -X PUT \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer <YOUR-TOKEN>" \ -H "X-GitHub-Api-Version: 2022-11-28" \ https://api.github.com/orgs/ORG/issue-types/ISSUE_TYPE_ID \ -d '{"name":"Epic","description":"An issue type for a multi-week tracking of work","is_enabled":true,"color":"green"}'

Response

Status: 200

{ "id": 410, "node_id": "IT_kwDNAd3NAZo", "name": "Task", "description": "A specific piece of work", "created_at": "2024-12-11T14:39:09Z", "updated_at": "2024-12-11T14:39:09Z" }

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4