Feature request: Setting specific permissions for Github Releases, or moving the permission one level up to Maintain
#156201
Replies: 2 comments
-
|
Hey there! 👋 Thanks for posting in the GitHub Community, @ramonvermeulen ! We're happy you're here. You are more likely to get a useful response if you are posting in the applicable category. The Accessibility category is a place for our community to discuss and provide feedback on the digital accessibility of GitHub products. Digital accessibility means that GitHub tools, and technologies, are designed and developed so that people with disabilities can use them. I've gone ahead and moved this to the correct category for you. Good luck! |
Beta Was this translation helpful? Give feedback.
-
|
💬 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.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
GitHub Feature Area
Repositories
Body
Following the permissions for each role model, with the current set-up if someone has
Writeon the repository he/she is allowed to create Github Releases.I was quite surprised finding this out, because to me it seems not logical at al. In my opinion Github Releases shouldn't be on the same permission level as writing to a repository. Let's say you work in a big team with a lot of new developers, this means that anyone with write permission on the repository can do a Github release. Let's say you only want to give a couple of more senior developers and/or the product owner permission to do a release, with the current set-up of the access management model this is not possible.
I would really love to see a feature where there will be a specific role for doing Github releases or that the permission is moved one level up to
Maintaininstead ofWrite.Beta Was this translation helpful? Give feedback.
All reactions