Feature request: Setting specific permissions for Github Releases, or moving the permission one level up to Maintain

[ramonvermeulen]

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 Write on 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 Maintain instead of Write.

[queenofcorgis]

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!

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐