jd__

7 ms·

1.
Becoming Standard: WebP's Late Victory and AVIF's Quiet Takeover(onelayerdeeper.substack.com)
3 points by jd__ 11mo ago|0 comments
2.
Application vs. Database: Where Should Permissions Live?(mergify.com)
1 points by jd__ 1y ago|0 comments
3.
by jd__ 1y ago
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.
4.
by jd__ 1y ago
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 written up publicly. The angle we took i
5.
by jd__ 1y ago
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 main before landing. That ensured a linear history
6.
The origin story of merge queues(mergify.com)
92 points by jd__ 1y ago|29 comments
7.
by jd__ 1y ago
I always expect that the shoemaker's children go barefoot.
8.
What I Learned Building My First Jenkins Plugin(mergify.com)
3 points by jd__ 1y ago|0 comments
9.
by jd__ 2y ago
Why's that?
10.
Streamlining Software Dependency Management with Dependabot(blog.mergify.com)
1 points by jd__ 3y ago|0 comments
11.
How We Scan Container Images for Vulnerabilities at Mergify(blog.mergify.com)
2 points by jd__ 4y ago|0 comments
12.
by jd__ 4y ago
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 support this. (Julien from Mergify)
13.
by jd__ 4y ago
Rather 1/5th of Mergify, and still in beta, but that's the spirit yes. :) (Julien from Mergify)
14.
by jd__ 4y ago
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 Uber engineers using Mergify on
15.
by jd__ 4y ago
I'd be curious to know what you find limited in off-the-shelf solutions? (disclaimer: I'm from the Mergify team )
16.
CPython Development Workflow Automation(medium.com)
2 points by jd__ 8y ago|0 comments
17.
A multi-value syntax tree filtering in Python(julien.danjou.info)
1 points by jd__ 8y ago|0 comments
18.
by jd__ 8y ago
We were using Gerrit and Zuul. We move to GitHub to have a lower barrier of entry for new contributors.
19.
by jd__ 8y ago
Fixed, thanks a lot!
20.
by jd__ 8y ago
Thanks! It does support all the merging feature that GitHub provides. There are features request already to support even more merge methods. :)
21.
by jd__ 8y ago
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 passes and the code has been reviewed and approved. That&#x2
22.
Show HN: Mergify – An automation platform for GitHub pull requests(mergify.io)
24 points by jd__ 8y ago|7 comments
23.
Scalable Metrics Storage: Gnocchi on Amazon Web Services(julien.danjou.info)
1 points by jd__ 10y ago|0 comments