-
Notifications
You must be signed in to change notification settings - Fork 60.6k
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
Improve Issue API documentation #35718
Comments
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
@beliaev-maksim Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛 |
Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀 |
I also think that this issue should be looked into |
Thanks for opening an issues al |
@beliaev-maksim Thank you so much for your patience while our SME team reviewed! They agree that this is a gap in the documentation, and we've filed an issue to address this internally 💛 While we are unable to use public issues for tracking, rest assured the team is now fully aware of this documentation gap, and will address this as soon as they are able ✨ Thank you again for raising the flag on this gap! |
Thanks |
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/rest/issues/labels?apiVersion=2022-11-28#add-labels-to-an-issue
What part(s) of the article would you like to see updated?
This API endpoint not only assigns existing labels but also creates a new label if it does not already exist. The newly created label will have a
null
description and a default color ofededed
. This is a convenient feature, and I believe it should be clearly documented to ensure users are aware and can take full advantage of it.Additional information
I believe this should be resolved in the internal repository. Could we use this issue as a tracking issue and keep it open until the internal issue is addressed?
The text was updated successfully, but these errors were encountered: