Issues

Where Warp stores its list of migrations

The Issues page of Migration HQ is the list of the Project’s migrations. For each repository that Warp finds in the sources you provide (e.g. Azure DevOps), it creates an issue representing that repository:

Viewing Open Issues

When you open Migration HQ’s Issues page, you will see the open issues list, which GitHub displays by default. Items in the open issues list correspond to repositories that have not yet been migrated:

The open issues list in the Issues page, which displays the Project repositories that have not been migrated.

To view an open issue, click its name. You will be taken to its issue page, which will display its details, and which you can use to issue commands, including the command to start a migration.

You can filter Migration HQ issues in the same ways you would in a standard GitHub repository: by open/closed status, author, label, and so on.

Viewing Closed Issues

Items in the closed issues list correspond to repositories that have either been migrated or ignored:

The closed issues list in the Issues page, which displays the Project’s migrated and ignored repositories.

To view an closed issue, click its name. You will be taken to its issue page, which will display its details, including information about the migration.

Closing Issues

There are two ways to close an open issue in Migration HQ:

1. Automatically. After a successful migration of a repository to GitHub, Warp changes the status of its corresponding issue to Closed. The issue will move from the open issues list to the closed issues list, and the Closed indicator will appear below the title of its page:

   
2. Manually. You can close one or more issues manually by checking their boxes in the open issues list and selecting either Completed or Not Planned from the Mark as menu:

   

   Marking an issue as Completed, which will cause the repository to be ignored.

   You can also manually close an issue on its own page — see Issue Page for details. By closing an issue manually, you are choosing to ignore the repository. Ignoring a repository has these effects:

• It moves the issue to the closed issues list.

• Warp will ignore any slash commands (commands that you issue to Warp) entered into the issue’s comments and it will not update the issue’s content.

Re-opening Issues

If you decided that you need to re-migrate a repository, you can do so by re-opening its issue. You can re-open one or more issues by checking their boxes in the closed issues list and selecting Open from the Mark as menu:

Marking an issue as Open, which makes it a candidate for migration again.

Re-opening an issue has these effects:

• It moves the issue to the open issues list.

• Warp will once again pay attention to slash commands entered into the issue’s comments and will update the issue’s content as its status changes.