Re: [git-users] Strict, domain-based read/write vs. read-only access.

Hi, Magnus, Does it help to identify this as a policy requirement, not a technical one? Our security and executive groups require that the only way we add or modify code is within the DEV environment/subdomain/call it whatever you want. You MUST NOT add code to a repository from any other envir

Re: [git-users] Strict, domain-based read/write vs. read-only access.

Hi, Magnus, The Enterprise I'm working at has separated its DEV, TEST, and PRODUCTION environments with firewalls. Code may be PUSHed to a Code Management System in DEV ONLY. In the TEST and PRODUCTION environments, the CMS repository MUST (cf. RFC-2119) be PULL ONLY. In proposing a CMS, I MUS

Re: [git-users] Strict, domain-based read/write vs. read-only access.

Hi, Chris, Thanks for the ideas. Unfortunately, I'm not sure they'll work for me. While these solutions provide authorization by project, I need something that will provide authorization by environment. I need to give an arbitrary user `push` access to a project from DEV, but refuse that same a

[git-users] Strict, domain-based read/write vs. read-only access.

Good Morning, I need to pitch an Enterprise level code management system. This system needs to have some fairly strict read-only vs. read/write requirements based on environment. I first asked this question in Stack Overflow