Why does creating a PR force me to create a label I do NOT want to create? #199604
Replies: 3 comments 3 replies
-
|
💬 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.
-
|
hey @rfalanga 👋 . how to confirm and fix it :
this isnt a general github bug affecting everyone,,,,,its specific to this repo's automation setup. if its not your repo ,id reach out to the repo owner /admin directly with a screenshot since they're the only ones who can actually disable or fix that workflow 💙💙💙💙 |
Beta Was this translation helpful? Give feedback.
-
|
Welcome to the GitHub Community, @rfalanga ! You are more likely to get a useful response if you are posting your question(s) in the applicable category. I've gone ahead and moved it for you. Good luck! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Workflow Configuration
Discussion Details
In the last few days, I have tried to create a PR to merge one branch into another, but somehow (I have no idea how) GitHub insists, in fact it demands, that I create a label which is my GitHub account name.
I have no idea how my GitHub account got into that "Apply labels to this pull request" field. But it will NOT let me do anything else with it!! Every time I delete my name from that field it immediately puts it back in. Over and over and over and over again. At this point I can never use any other label because GitHub.com will not let me.
How did this happen?
Why won't it let me stop it, get rid of this bogus "new label"?
Beta Was this translation helpful? Give feedback.
All reactions