Menu

1 / 2

Twenty-six against forty

DEV Community: go·Matt Cockayne·10 days ago
#F5U48Ad3
#devtogo#devto#dev#merge#morning
Reading 0:00
15s threshold

I went to bed at about half nine, and the last thing I typed to the session before I did was this:

I am going to head off to bed now, but I would like you to continue the rollout and create all the MRs for waves 1-5, but do not merge them, we will review together in the morning .

The whole governance model is in that last clause

An estate-wide migration off a third-party errors library onto our own, across dozens of modules. It's mechanical and tedious, just the kind of job you want to hand over, and just the kind that goes badly wrong without making a sound.

I could hand it over and then sleep because everything up to the merge button is recoverable... a branch, a merge request, the lot. Forty merge requests sitting open overnight are, at absolute worst, forty things to close in the morning (and a mild feeling of having wasted an evening's compute).

The merge is where it stops being recoverable, so the merge is where the stop went.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.