Permissions for locking branch without admin #147016
Unanswered
kfirg-cetu
asked this question in
Repositories
Replies: 1 comment
-
h, I see what's going on! This is a common issue when working with multiple GitHub accounts and repositories. Let me break it down in a more conversational way. The reason your commits are showing the GitHub account owner's name (your friend's name) instead of your local user.name and user.email is likely because GitHub is associating the commits with the email address tied to your GitHub account, not the one you set in your local Git config. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Question
Body
As part of our workflow we have points in time in which we like to lock down a branch for merges.
This is mostly performed during large releases / big conflicts.
Luckily there is a feature on GitHub that allows locking branches, such that no one can merge to a locked branch.
The problem is that there is no way to grant this specific permission. I.e there is no option (or at least not one that I found), that can just control the "lock branch" feature on certain branches. This means that only repository admins can perform this action.
Providing a custom role that can do this action will be very beneficial.
Beta Was this translation helpful? Give feedback.
All reactions