Issue Page

​

Overview

Each issue in Migration HQ represents a repository, where:.

• The body of the issue displays detailed information about the repository, including its status.
• The comments act as Warp’s user interface, where you enter commands and get responses.

​

Issue Name

When Warp creates an issue for a repository to be migrated, it assigns the issue a name using the following format: [source][repository_name]

• source represents the source of the repository to be migrated (e.g., Azure DevOps).
• repository_name is the name of the repository, as specified in the source.

Repositories that have not yet been migrated are marked with GitHub’s Open indicator… …and repositories that have been migrated or ignored are marked with GitHub’s Closed indicator:

​

Start of Body

The issue’s body begins with the author attribution. Any issue or comment generated by Warp is attributed to the user packfiles-warp, followed by a rough date for when the issue was generated (e.g., “opened last week”): After the attribution, the first line of the issue’s body specifies the purpose of the issue: The line follows the format “This tracks the migration of the [repository_name] repository from [source_system] to GitHub” where:

• [repository_name] is the name of the repository as it appears in its source system.
• [source_system] is the name of the system that the repository is being migrated from (e.g., Azure DevOps).

​

If the Migration Is Ignored

If the migration is ignored (i.e., manually marked as Completed or Not Planned), the “⚠️ This Repository Has Been Ignored ⚠️” message appears at the start of the body: The message informs the user that:

• Since the issue was closed manually, its repository will be ignored.
• Because the repository is ignored, Warp will ignore slash commands typed into the comments and will not update the issue’s comments.
• The repository can be “un-ignored” by manually changing its status from Closed to Open, which can be done at the bottom of the issue page or via the Mark as menu in the closed issues list (see Issues).

​

Migration Status

The Migration Status section contains:

• The current status of the repository (e.g., “not started”, “complete”).
• A checklist of tasks that need to be completed in order to complete the migration. Warp will automatically check tasks off this list as they are completed.

​

About

The About section, when expanded, lists details about the repository on the source system. It contains:

• The date when the last commit to the repository was pushed.
• The number of commits made to the repository in the last year.
• The name and email address of the repository’s most active contributor.
• The size of the repository.

​

Source & Destination

The Source & Destination section, when expanded, provides links to the source and destination repositories. It contains:

• The name and link for the source repository.
• The name of the destination repository, and if the repository has been migrated, the link to the destination repository.

​

Inventory

The Inventory section, when expanded, displays information about the migrated repository, providing the date and time when the repository was migrated as well as a link to the destination repository: In an issue for a repository that hasn’t yet been migrated, the Repository Content section simply displays that the repository has not yet been migrated to GitHub:

​

Help & Support

The Help & Support section appears near the end of the issue’s body. When expanded, it lists the ways you can get help while using Warp. It provides links to the following resources:

• The Warp Knowledge Base.
• GitHub’s Copilot docs (Warp works with Copilot chat — open it and try sending questions to @packfiles-warp!).
• The link for Packfiles Support.

​

End of Body

The issue’s body ends with the following:

• GitHub’s Create sub-issue / Add existing issue and emoji menus.
• Author attribution (once again, any issue or comment created by Warp will be attributed to packfiles-warp).
• Any labels for the issue, whether they were added by Warp or a user.
• A rough date for when the issue was generated (e.g., “opened last week”).

​

Comments and Slash Commands

In any issue created by Warp, comments serve an additional purpose: they’re your interface for issuing migration commands. Commands to Warp are called slash commands because they start with the “slash” (/) character. You’ll find the full list of slash commands on the Slash Commands documentation page.

​

Simple Migration Example

Here’s an example of a repository migration. To migrate a repository, you would open its issue page, scroll to the comments section, and enter the /migrate command into the comment box as shown below: Seconds later, Warp will respond with a comment informing you that the migration has started, and that it will notify you when the process has completed: When the process is complete, Warp will post another comment informing you that the migration was successful. The comment will include a link to the new migrated repository: Warp automatically closes a repository’s issue after it has been migrated. The issue’s “closed” status will be indicated in the issue’s title and in a notice in the comments, which will also provide a rough date for when the issue was closed (e.g., “1 minute ago”):

​

Ignoring a Repository

You can choose to ignore repositories that you don’t want to migrate. You can mark an issue as ignored by clicking the Close issue button in its comments section… …or by checking its box in the closed issues list and selecting Open from the Mark as menu: