-
Notifications
You must be signed in to change notification settings - Fork 119
Description
Description
I am using the latest version of github/gh-ado2gh 1.19 and I am able to generate the migration script for moving repos from ADO to our own GHE enterprise, the repo's move over generally without issue however the pipeline re-wiring just doesn't seem to work anymore.
Here's an example of the logs for the rewiring step for a repo using the classic pipelines.
[2025-10-01 13:51:37] [INFO] Rewiring Pipeline to GitHub repo...
[2025-10-01 13:51:37] [INFO] Looking up pipeline ID for: \EmailService - PR Dev
[2025-10-01 13:51:38] [INFO] Using resolved pipeline ID: 187
[2025-10-01 13:52:39] [WARNING] HTTP error during branch policy check for pipeline 187 in EmailService: Response status code does not indicate success: 404 (Not Found).. Pipeline trigger configuration may not preserve branch policy requirements.
[2025-10-01 13:52:39] [INFO] ADO Pipeline ID = 187 is NOT required by branch policy - preserving original trigger configuration
[2025-10-01 13:52:39] [WARNING] HTTP error retrieving pipeline 187 in [project]: Response status code does not indicate success: 400 (Bad Request).. Skipping pipeline rewiring.
[2025-10-01 13:52:39] [INFO] Successfully rewired pipeline
[2025-10-01 13:52:40] [WARNING] GitHub is currently experiencing availability issues. See https://www.githubstatus.com for details.
There is a branch policy in place but it seems like this isn't detected and the pipeline isn't even updated to use our GHE even if the status check hasn't been configured.
Reproduction Steps
Run a rewire-pipeline command using PAT token authentication for ADO and GHE
gh ado2gh rewire-pipeline --ado-org "{org-name}" --ado-team-project "{project-name}" --ado-pipeline "{pipeline-path}" --github-org "{gh-org}" --github-repo "{repo}" --service-connection-id "{connection-id}"
and get the above output in response.
Manually re-wiring
In an attempt to re-wire the pipeline just so that the repo and pipeline have been moved together for this repo I updated the pipeline to point to the relevant GHE repo and added the status check for a PR, however when a PR is raised the status just get's stuck saying "Expected — Waiting for status to be reported", if I manually trigger the pipeline for the relevant branch the status updates in GH so it seems like the PR trigger isn't working in ADO as I can see the webhook request was sent with a 200 response.
Any help with this would be great - thanks in advance,
Adam