Top all-time · #7298
Mergify
Company blog · mergify.com/blogprogrammingsystems
Mergify is the company blog at mergify.com, writing about programming and systems. Since 2022, 10 different Hacker News readers have linked it 17 times, most often “Application vs. Database: Where Should Permissions Live?”. It is still writing: the last post was on 2026-10-28, and you can follow it by feed.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
HN readers link Mergify as a merge-queue vendor in pull request workflow discussions, and its blog for posts on Python coroutines and async behaviour. Comments mostly cite the company rather than judge the writing.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Mergify - Reliable CI pipelines for fast-moving engineering teams
Most-linked posts?
- Application vs. Database: Where Should Permissions Live?2 people · 2 mentions · first linked 2025-09-18
- What I Learned Building My First Jenkins Plugin2 people · 2 mentions · first linked 2025-09-09
What Hacker News says?
Woah that's actually huge. I've been very interested in tangled from an atproto perspective but I had no idea it had that as well. Wonder why that isn't talked about more. Seems like an amazing feature to potentially pull some people away from GitHub/GitLab after they've have been asking for years for a better stacking workflow. I've been going through a lot of different git stacking tools recently and am currently…
Comment linking /
on “Graphite is joining Cursor”Submitted The origin story of merge queues as a story · 92 points
HN discussionThis is a real problem in my current place (huge monorepo, 100+ devs, 100+ merges per day). Like others said, "merge queue" is the solution. GitHub's one has been in beta for many months now. There are also dedicated companies doing this like https://mergify.com/ But there's several tricky aspects like "what if I want some commit to jump in front of queue?", compliance etc. Due to the multitude of requirements and o…
Comment linking /
on “Ask HN: How are pull requests integrated in a repo with high commit frequency?”Submitted Await Is Not a Context Switch: Understanding Python's Coroutines vs. Tasks as a story · 78 points
HN discussion> So the author's point is that "other" can never appear in-between "parent before" and "child start". But isn't it true for JavaScript too? So I don't really get the author's point... am I missing something or the author('s LLM?) forced a moot comparison to JavaScript? Edit: after reading the examples twice I am 99.9% sure it's slop and flagged it. Edit2: another article from the same author: https://mergify.com/bl…
Comment linking /blog/why-warning-has-no-place-in-modern-logging
on “Await Is Not a Context Switch: Understanding Python's Coroutines vs. Tasks”Submitted Origin and Evolution of the Globstar as a story · 9 points
HN discussionSubmitted Application vs. Database: Where Should Permissions Live? as a story · 7 points
HN discussionSubmitted Monorepo CI for GitHub Actions: Run the Tests You Need, Nothing More as a story · 6 points
HN discussionSubmitted What I Learned Building My First Jenkins Plugin as a story · 6 points
HN discussionSubmitted A Markdown File Became Our Company's On-Call Runbook as a story · 5 points
HN discussionSubmitted Lessons from a Noisy Monitor as a story · 5 points
HN discussionSubmitted Claude Didn't Kill Craftsmanship as a story · 4 points
HN discussionSubmitted What I Learned Building My First Jenkins Plugin as a story · 3 points
HN discussionSubmitted The Native TypeScript Compiler Cut Our Typecheck from 13s to 3.5s as a story · 2 points
HN discussionSubmitted AI writes code that breaks main half as often as a story · 2 points
HN discussionSubmitted AI writes code that breaks main half as often as a story · 2 points
HN discussionSubmitted Application vs. Database: Where Should Permissions Live? as a story · 1 points
HN discussion
