"Using Git has made our team much better by removing barriers to collaboration and code reviews. Those are the real Git benefits, not specific features like fast branches."
Which brings me to another point: I'd love to hear someone talk at one of our meetings about real world experience using git (and git-connected tools) for code review within an organization - and not in an open source project where it is more or less necessary, but something more like a work environment where code reviews are part of a development workflow.
- Jason
Jonathan "Duke" Leto
unread,
May 29, 2013, 1:21:43 AM5/29/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to pdx...@googlegroups.com
Howdy,
Have you ever seen Gerrit? Take a look at the public CloudFoundry instance:
It is a high-powered system built on top of Git which was written by
Shawn Pearce at Google to manage the development of the Android
project. It has an extremely advanced system of decided how and why
code should be promoted to master or other specially designated
branches.
You can tell it that certain people must approve certain branches
(such as lawyers or security auditors) or that certain automated test
suites must pass for code to be promoted to production.