Viewing profile — jd__

FWIW, Mergify's Merge Queue supports this as long as you run it without batching or parallel checks. We expose a config option for semi-linear history while still keeping CI green.…

That's super interesting, thanks for sharing the Yelp/PayPal lineage. You're right: there's probably a lot of prior art in internal release engineering systems that never got much …

That's a good point. To clarify, Gerrit itself didn't actually do merge queuing or CI gating. Its model was stacked commits: every change was rebased on top of the current tip of m…

I always expect that the shoemaker's children go barefoot.

Why's that?

Best way is to batch your PRs in a single CI run. That saves CI time and increase your throughput. It does not seem GitHub merge queue supports this, but some merge queues do suppo…

Rather 1/5th of Mergify, and still in beta, but that's the spirit yes. :) (Julien from Mergify)

We know Uber has some great internal tooling (there's even a paper published on their merge queue: https://eng.uber.com/research/keeping-master-green-at-scale/ ). We had various Ub…

I'd be curious to know what you find limited in off-the-shelf solutions? (disclaimer: I'm from the Mergify team )

We were using Gerrit and Zuul. We move to GitHub to have a lower barrier of entry for new contributors.

Fixed, thanks a lot!

Thanks! It does support all the merging feature that GitHub provides. There are features request already to support even more merge methods. :)

A few months ago, we moved a project to GitHub and missed the automation we used to have on the old platform. For example, we like to merge pull requests automatically when the CI …