Review Dependencies

Review Dependencies

Open Review dependencies from the Migration Plan journey, under Organize. It reads the direct references between the plan's repositories — pipeline templates, repository resources, submodules, checkouts, triggers, hard-coded URLs, and Azure CLI commands — and shows what each wave's move touches.

The step checks that nothing a wave references moves after it. Done when counts the references to repositories that move in a later wave, or in no wave, and the wave pairs they fall in. That item is not required: a reference to a repository that moves later stays on Azure DevOps and is rewired again when its target moves. Move the targets into the earlier wave to rewire it once instead.

The tiles across the top count the references rewired twice, the project pairs that work together, the small groups split across waves, and the most used repository. Choose which reference types the views show; keep at least one. Done when always counts every type.

Between Waves

Between waves lists the wave pairs whose references point at a repository that moves later, or in no wave yet. Each pair says which projects it connects and lists the repositories it references too early.

Move it into wave N, or Move these N into wave N, pins those repositories into the pair's first wave, so the references are rewired once. Their own references are checked again after the move. A pair that references more than 25 repositories is too many to pin one at a time: open its list and move them all together, or move their projects on Schedule Waves.

Show the full matrix sets every wave against every other, with no wave last. The cells above the diagonal that are highlighted are the pairs rewired twice. A cell is one of:

• Same wave — rewired together
• Target moves first — rewired once
• Target moves later — rewired twice
• Referrer has no wave — neither side is scheduled

Blast Radius

Blast radius shows what moving one repository touches. Search for any repository by name or project; the most referenced come first.

• The repositories that use it directly — edited when it moves. Those in the same wave are covered by its rewire. Those in other waves, or in no wave, each get a separate update pull request.
• The repositories that use those — not edited, but their builds use something that is. Worth a smoke test when the wave lands.
• What it uses — the repositories it references.

Each ring is split into the same wave, other waves, and no wave yet. Select a repository in a list to see its details and its own blast radius.

Between Projects

Between projects lists pairs of projects whose repositories reference each other directly, counted one hop between repositories, with the shared hubs left out, biggest first. A pair is worth a look when the project it uses moves later, so its references are rewired twice, or when the two land in different orgs.

Show All pairs, the pairs Rewired twice, or the pairs that land in Different orgs, and search by project. Each pair says whether the two move together, earlier, or later, and whether they land in the same org. Settle a pair that crosses orgs on Cross-org References.

Small Groups

Small groups are repositories inside one project that reference each other directly, with shared hubs left out: groups of 2 to 5, and of 6 to 40. Each one should move in one wave, so its references are edited once. Larger groups move with their project.

A small group split across waves is listed with its fix: keep it together in its earliest wave. A group is usually split by a pin or a wave rule.

Shared Hubs

A shared hub is a repository more than 40 others reference directly. Hubs are left out of the project pairs and small groups, and the page lists them on their own with the wave each moves in. Move each one in the first wave that needs it.

A hub's Azure DevOps copy stays enabled until the whole migration finishes, so pipelines that haven't moved keep working. Until then, a change to one has to be made in both places.

The Repository Tables

The repositories behind a wave pair, a group, or a blast radius open in the same table as Plan Repositories, limited to that list, with its own search and filters. Select a repository to open its panel and send it to another org or wave, or select several and move them to a wave together.

The view, the open wave pair or group, the blast radius repository, the reference types, and the search stay in the address, so you can reload or share the link.

The Dependency Findings report carries the same findings for people outside the plan.