Prerequisites
Before using the Packfiles GitHub Copilot Agent, ensure that:- Your Migration HQ repository has been initialized by Warp and a source scan has completed successfully, so that backlog issues have been created for your repositories
- GitHub Copilot is enabled for your organization
- Packfiles Warp App is installed on your Migration HQ organization
- You complete the setup steps outlined below to give the agent the necessary permissions to operate in your Migration HQ repository
Setup
To configure the agent for your Migration HQ repository:-
Add the following GitHub MCP configuration under
Migration-HQ → Settings → Code & automation → Copilot → Coding agent:Ensure you’ve saved the configuration before proceeding to the next step. -
Create a fine-grained PAT with:
- Issues: read+write
- Pull requests: read+write
Migration-HQrepository only. -
Add the PAT as a secret named
COPILOT_MCP_GITHUB_PERSONAL_ACCESS_TOKENin theMigration-HQrepository underSettings → Secrets and variables → Agents. - Follow the instructions in the GitHub documentation to enable agent apps at the Enterprise level.
What the Agent Can Do
The Packfiles GitHub Copilot Agent has three capabilities, each invoked from a different entry point in Migration HQ:
The agent supports both Azure DevOps and Bitbucket Server migrations, including projects with a mix of both sources.
Further Reading
- Migration Planning — Plan your migration waves and generate a strategy document
- Migration Diagnosis — Diagnose and fix failed migrations
- Validate Configuration — Validate and author
config/warp.ymlchanges