3 ms·
It’s risky but at the same time it allows creating a significant spike of value without spreading thin. Like, github PRs are pretty shit, which is an opportuni
by masklinn 3y ago
It’s risky but at the same time it allows creating a significant spike of value without spreading thin.
Like, github PRs are pretty shit, which is an opportunity for reviewable.
- maccard 3y ago> Like, github PRs are pretty shit, which is an opportunity for reviewable. I've used a bunch of VCS's and managed solutions, and PR's are probably the _best_ I've had the pleasure of using. Working with perforce, everyone is one (or a small number) of long lived branch(es), chucking around WIP code as shelves. PlasticSCM/Unity DevOps Version Control (seriously, that's what they renamed it to) provides absolutely no support for a merge-based workflow other than some half-baked tools that barely work.