Skip to content

gh ado2gh migrate-repo support for Azure devops Server on-prem #1399

@fairmonk

Description

@fairmonk

Does this tool support migration of repository from azure devops server on-prem installation ?

What I tried:

1. Exporting PAT token env variables
root@pt-deb01:~# export GH_PAT="ghp_FGp82XUcek43gfdDcg1hPld3dvgZqx32l5mB" root@pt-deb01:~# export ADO_PAT="s9ldha34fmxv625rjfi3h44o6t4lfvpwnkgy7nos5a2bgktcrswq"

2. Run migration command:
gh ado2gh migrate-repo --ado-org https://azuredevops.mycompany.local/DefaultCollection --ado-team-project ProjectName --ado-repo repo-name --github-org org-name --github-repo repo-name

Error inside verbose log file:
[2025-07-28 12:54:05] [DEBUG] RESPONSE (OK): {"data":{"node":{"id":"RM_kgDaACRjOWE4MDUxYi04NDY0LTQ1YjYtYTM3NC1mZmQwMzNhNzliNWE","sourceUrl":"https://dev.azure.com/https%3A%2F%2Fazuredevops.mycompany.local%2FDefaultCollection/ProjectName/_git/repo-name","migrationLogUrl":"","migrationSource":{"name":"Azure DevOps Source"},"state":"FAILED","warningsCount":0,"failureReason":"PreflightCheckJob failed due to network availability issues. Please try again in 30 minutes. If this happens repeatedly, please contact GitHub Support.","repositoryName":"repo-name"}}}

obviously what happens is that the ado2gh extension appends the https://dev.azure.com to my company on-prem ADO server and I don't need that. How to overcome this ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions