Plan Repositories

The Repositories Table

The plan's Repositories page lists the plan's repositories. A number elsewhere on the plan opens this same table, already filtered to the repositories that number counts.

The table loads one page at a time, up to 100 repositories, so a large estate stays usable. Each row shows where the repository lands, which wave it moves in, and whether that came from the project, a rule, or a choice on the repository itself. It also shows the dry run and how the repository moves, including when no dry run has copied it yet.

Copy time is the measured dry-run time when a dry run recorded one, and an estimate from the repository's size and pipelines otherwise. Open a repository to see the latest copy: the dry run's number, how long a failed or still-running copy took, and a link to the copy in the sandbox organization on GitHub when there is one.

Filter and Sort

Search the list, then narrow it. Filters combine, so a repository has to match every filter you set. You can filter by project, destination, wave, and source, and by the dry run, what it found, how the repository moves, an exception to its project, a reference to another org, a change since the dry run, or Git LFS.

Each option shows how many repositories it holds given your other filters. That count leaves out the filter you are looking at, so the other options still show how they split the list. Sort by name, project, size, pipelines, or how many other repositories use it.

The filter stays in the address, so you can reload or share the link and keep the same list.

You can also narrow the list to repositories that would share a name in a destination org. Settle those names on Decide Destinations.

Changed since the dry run matches a finished copy whose source has changed since that copy. Open the repository to see how many branches and tags were added, deleted, or moved, and how many pull requests were opened, closed, reopened, or pushed to. A copy that was not compared, could not be read, or has no record of the source from before the copy does not match. See Keep copies fresh.

Assign a Destination or a Wave

Assign the rows you select, or every repository the current filter matches. Every match includes repositories on other pages, except the ones you leave out.

You set a destination, a wave, or both. Whichever you do not set stays as it is.

For the destination, choose an org, no destination, or to follow the first matching rule — or the project, when no rule matches. For the wave, choose a wave, or follow in the same way. Choosing to follow clears a choice set on the repository itself.

A repository keeps a choice of its own only when it differs from that rule or project. Assigning the destination or wave it already has does not store a separate choice. The row shows what it would inherit if you cleared its own choice, and it is marked when it lands in an org other than its project's, or moves in a wave other than its project's.

If the plan changed since you loaded the list, or the repositories the filter matches are no longer the ones the page showed, the assignment does not apply. Check the list and try again.