### Summary

gh gei generate fails on a specific GHES organization: the REST GET call used to fetch repo names on the source GHES org returns nothing or 404, so the PowerShell output script is not generated.

The same command and PAT work:

• On other GHES organizations
• When swapping source/target with a dummy GHEC org
• When using gh gei migrate-repo directly with repo ADMIN permissions (which succeeds as expected)

Environment

• GEI CLI (gh-gei) version: v 1.28.0
• gh CLI version: Latest
• Source: GitHub Enterprise Server (GHES) v 3.8
• Target: GHEC latest
• PAT type: Classic (legacy) PAT
• PAT scopes:
  • repo
  • admin:org
  • read:org
  • workflow
  • user all

What I am doing

Command (redacted):

GH_ENTERPRISE_TOKEN=<legacy_PAT> \
gh gei generate \
  --source-url https://ghe-source.mycompany.com \
  --source-org <problem-source-org> \
  --target-org <target-org> \
  --output migrate.ps1 \

logs written to vscode!

Expected behavior

• gh gei generate lists repositories from the source org via REST API.
• The PowerShell script (migrate.ps1) is generated for that org.

Actual behavior

• For this specific GHES org:
  • Verbose logs show REST GET calls to the source GHES API, but the GET that should list repos does not retrieve repo names.
  • As a result, the script is not generated.
• For other orgs:
  • The same token, same user, same command successfully fetches repo names and generates the script.
• For a dummy org on GHEC / swapping source and target:
  • Script generation succeeds.
• Using gh gei migrate-repo directly:
  • Repo migration works with only repo owner permissions, which appears to be the intended behavior.

Logs / diagnostics

GET https://ghe-sourceorg.myfirm.com/api/v3/orgs//repos
->
404