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 environment/subdomain. What if you're in the TEST environment and you find a bug? Fix it in DEV, promote the change, and test again. What if you're in the PROD environment and your shiny new web application crashes because it couldn't handle the load? You MUST NOT modify that code on the fly and update the repository from PROD. You MUST take that error back to DEV, update your code there, TEST it, and then promote the fix back into PROD. Does that help? David > On Jan 7, 2016, at 14:37, Magnus Therning <mag...@therning.org> wrote: > > So you basically want to include the source IP address in the decision > of whether a push succeeds? > > I'm sorry but this sounds *amazingly* strange to me. Probably because I > don't quite get what you mean. > -- David - Offbeat dafydd - Online http://pgp.mit.edu/ ----5----1----5----2----5----3----5----4----5----5----5----6----5----7-- The most dangerous phrase is, 'We've always done it this way.' –RADM Grace Hopper -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Description: Message signed with OpenPGP using GPGMail