Jump to content
Please Use CODE Tags

Controlling and managing separate git repos on Azure DevOps for code security

Laaazz
By Laaazz
in Programming
 Share
Posted

My company is about to onboard some junior devs for the first time, and we want to limit their access to just the presentation layer. As it stands, everything is in one Git repo. The current plan is to fork the main repo, and modify it such that only presentation layer and the compiled assembles will be left. The new devs can then branch from there. The lead dev can just do the merge himself.

Is there a better and optimal way to approach this?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

On alternative software like git lab, there's a permissions section that you can assign roles and also modify role permissions. 

 

For example:

By default maintainers are the only ones that can modify master. Developers can make changes and guests can't push any changes at all. 

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Programming

×