2 ms·
So this is mostly about Gitlab EE/Github Enterprise in an enterprise setting: 1. Control of your data. You get to keep your code on your servers and don't have
by Macha 8y ago
So this is mostly about Gitlab EE/Github Enterprise in an enterprise setting:
1. Control of your data. You get to keep your code on your servers and don't have to worry about Github themselves being breached.
2. PR workflows to enforce code reviews. Also a central place to view them. Also it links to JIRA so you can go from a ticket to a code review.
3. Finding internal clients (more useful for big companies were you might not know all of them). "Hey, there's a security bug in InternalLib 3.5 and we need everyone to update to 3.6. Who's using it?". Hey, who owns/uses "m-asd-indexer.dc1.mycompany.com".
4. Familiarity. Most devs these days are at least aware of how open source github workflows work, as opposed to email + patches or other approaches.
5. Global search. "Oh, hey, InternalProcessor 4.6 is doing something odd when we call internalDooDad.foo(bar) . Let's go search for that and figure out if we can understand the behaviour". "Hey, we've standardised on service X for access control, how have other projects integrated it?"
- grogenaut 8y agoHow do they help with #3?