-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT]: allow issue Type management via the REST API client #466
Comments
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with |
Blocked by octokit/openapi#452 |
in the meantime, you can manually use the endpoint with |
Coming back to this, it seems you are wanting new features on the REST endpoint. You can request new features here: |
Good point. I started a new discussion here: I'll come back here once the option is available in the API, and then maybe we can add a new wrapper for it in Octokit. |
Describe the need
GitHub recently introduced "Issue Types", a new way to categorize and filter issues per type.
The change was announced in this blog post, and is detailed in https://github.com/orgs/community/discussions/139933
It is already possible to add a type to an issue via the GraphQL API: there is an
IssueType
object to manage issue types at the organization level to create, update, and delete them.It would be nice if a similar option was added to the REST API Client, as part of
issues
.SDK Version
No
API Version
No
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: