I have a Visual Studio Online account and multiple projects.
On each project I would like to choose who can commit into different branches. For example, I would like the lead developer to be the only person who can commit to 'master' which will then kick off a CI build.
I want to ensure that, when I'm using freelancers, that they can't merge into the 'master' or 'staging' without code review and testing.
Visual Studio Online has a set of granular permissions that you are able to set at the Git repo & branch level.
You can create custom security groups within your team projects and then assign them permissions. There are built-in security groups that you want (like Contributors
) to ensure don't provide additional permissions to users than what you want for them so make sure that you look at it more broadly. For example, you can begin to remove permissions from the Contributors security group and begin adding permissions to other custom security groups. The main thing is that you can setup permissions to meet your goals.
Here's some more information about the permissions available for Git repositories in http://msdn.microsoft.com/en-us/library/ms252587.aspx#Git. Look up towards the top for an overview of security in TFS in general.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With