# How to Manage Pull Requests Across GitHub Repositories

> A shared view helps, but every pull request still needs an owner and a next action.

- Author: PRLane Editorial
- Published: 2026-11-19
- Updated: 2026-11-19
- Canonical: https://www.prlane.com/blog/manage-pull-requests-across-github-repositories

An API change is approved. The matching frontend change is waiting for review. A shared package update is failing a check. Each repository looks manageable on its own, yet the feature cannot ship.

That is the practical challenge of managing pull requests across GitHub repositories: the work crosses boundaries that repository-specific lists do not explain. A useful process makes those relationships visible without turning every morning into a meeting.

## Start with the decision you need to make

A cross-repository overview should help someone choose their next action. Build your routine around three questions:

- What is ready for attention now?
- What is preventing the next step?
- Who owns that step?

Avoid making “open” your most important category. An unfinished draft, a change awaiting security review, and an approved documentation correction need different treatment. Combining them into a single backlog count makes the number larger without making the decision clearer.

[PRLane's fleet dashboard](https://www.prlane.com/) brings GitHub pull requests from multiple repositories into a shared view. Use that visibility to support a working agreement, rather than treating a dashboard as the agreement itself.

![Each repository feeds one action-oriented triage view.](https://www.prlane.com/blog/launch/manage-pull-requests-across-github-repositories-figure.png)

## Give every blocked change an actionable handoff

Consider a hypothetical checkout feature spanning three repositories. The API introduces an optional field, the client starts sending it, and documentation explains the behavior.

A useful handoff for the client PR might read: “Waiting for API change 184 to be available in staging. Maya will verify compatibility before requesting final review.” That explains the dependency, owner, and next event. “Blocked on backend” leaves the next person to reconstruct all three.

Put cross-repository dependencies in PR descriptions or linked tracking items. Distinguish merge order from deployment order. A change can be safe to merge before another service deploys if it remains backward compatible; a shared overview cannot decide that architectural question for you.

## Run a short, repeatable triage pass

Work through the same sequence each day:

1. Find urgent changes with a known business or operational reason to move first.
2. Identify ready work that needs a final decision.
3. Assign the next step for blocked work.
4. Revisit older changes whose intent or ownership has become unclear.
5. Remove obsolete work only after confirming it is no longer needed.

Age is a prompt for investigation, not an automatic priority score. A two-week-old experiment may matter less than a small compatibility fix holding up a release.

Keep the routine short by recording decisions where the team already works. A second spreadsheet that needs constant reconciliation can recreate the fragmentation you are trying to eliminate.

## Measure waiting, not just activity

Track how long changes spend waiting for review, waiting for fixes, and waiting after approval. Look for recurring handoff problems before setting a speed target.

If API work repeatedly waits on one reviewer, adding more coding capacity will not address that queue. If otherwise finished features wait for coordinated deployments, the improvement may involve compatibility planning rather than faster reviews.

Start with one group of related repositories and a consistent daily pass. Expand when the process produces clearer decisions, not merely a bigger dashboard.

Related guide: [A Practical Kanban Triage Routine for Pull Requests](https://www.prlane.com/blog/kanban-triage-for-pull-requests).

[Sign up for PRLane](https://www.prlane.com/sign-up) to bring your pull request fleet into one place.
