Implement Granular Security to Limit who can Push to Git - Status changed to: Declined

[#1]

Description - When a person is given Developer access they can pull and push to the Adobe Git instance for the program. There should be an option to prevent people with the Developer access to push when there is a customer Git repository that syncs to the Adobe Git

Why is this feature important to you - To prevent a customer Git repo becoming out of sync with the Adobe Git repo, there should be an option to not let people in the Developer role from pushing to the Adobe Git repo. 

How would you like the feature to work - Add an option to the Developer role to prevent pushing to the Adobe Git repo.

Current Behaviour -

[#2]

I don't think that this feature is really required, because you can always do a force-push from your own git to the CloudManager git. That means that any push directly into the CM git by a developer will be overwritten.

[#3]

Based on Joerg's comment that we can always do a force-push from our own git to the CloudManager git. That means that any push directly into the CM git by a developer will be overwritten.

[#4]

Hello @JimSzubryt 

Thanks for submitting this feature request, however, this request does not seem to be directly related to AEM product hence we mark this accordingly. We trust this could potentially benefit other users if raised to the proper team.