The Pattern
Every engineering team that works across more than a dozen repositories eventually hits the same wall: a pull request sits open for days — sometimes weeks — not because anyone rejected it, but because no one saw it.
The developer who opened it assumed the assigned reviewer got the notification. The reviewer was heads-down in a different project and missed it in a flood of GitHub emails. The engineering manager had no reason to check that specific repository on that specific day.
The PR wasn't blocked. It was invisible.
Why This Keeps Happening
Modern engineering teams distribute work across dozens or hundreds of repositories. Microservices architectures, monorepo-to-polyrepo migrations, and multi-team ownership structures all contribute to a world where no single person has a complete mental model of where active work is happening.
GitHub and GitLab notifications are designed for individual contributors tracking their own work. They're not designed to give anyone — developer, reviewer, or manager — a cross-repo view of what's open and aging.
Some teams build Slack integrations or custom bots. These work for a while, but they tend to become another source of noise. When a channel posts 30 PR updates a day, people mute it. The signal-to-noise ratio collapses.
The Actual Problem
This isn't about lazy reviewers or careless developers. It's a tooling gap. The default experience for managing PRs across multiple repositories provides no aggregated view, no age tracking, and no prioritization.
Without that, you're relying on individual vigilance to compensate for a systemic blind spot. That doesn't scale.
What Good Looks Like
The fix is straightforward in concept: aggregate every open PR into a single view, sorted by age and risk, with enough context to act without clicking through to each repo.
This is the core idea behind tools like Code Board, which pulls PRs from GitHub and GitLab into one Kanban board with automatic risk scoring and staleness tracking. But regardless of what tool you use, the principle matters: visibility should be a default, not a side quest.
The Takeaway
If PRs are going stale on your team, resist the urge to blame individuals. Look at the system instead. Ask whether your tooling gives anyone a complete picture of what's waiting for review across all your repositories.
If the answer is no, that's where the problem lives.
Top comments (0)