create issue + set new labels + no push access = fatal error, but the labels should be silently ignored #197408
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
Body
the github API docs for create an issue say:
this part is interesting:
because when i try to create a new issue (with new labels)
in a repo where i have no push access
then the request fails with HTTP status 403 forbidden
new labels, as in: the labels do not-yet exist in the repo
as i understand the docs
the API should just ignore all labels
when i try to create an issue in a repo where i have no push access
no matter if these labels exist in the repo or not
no matter if i am trying to create new labels or trying to use existing labels
the API should be less strict here
Beta Was this translation helpful? Give feedback.
All reactions