Rant time: today I'd like to talk about feature branching and GitHub—how we got here, what they are (and aren't) good for, why that matters, and what you can do instead. Join me, friends! /1
Show this thread
-
That's what CI is: developers merging to master, often working in pairs, and shipping artifacts, _at least_ once a day. Here's what it's not: a piece of infrastructure, something your DevOps team does for you, or running tests against your feature branches. /3
Show this thread
The "shipping artifacts" bit is interesting for libraries, since often merging into master is effectively shipping an artifact if you're working in a language that makes pointing at git repos for dependencies easy. Otherwise you need a nightly infrastructure which is a pain...