gh-gei
gh-gei copied to clipboard
Migration CLI for GitHub to GitHub migrations
## Description When communicating with customers on-prem servers (e.g. BBS or GHES) it's possible they have configured them to require client certificates (we had at least one ticket from a...
A couple of months ago, we changed the CLI's defaults so that, when migrating a repo, we wait for the migration to finish by default, rather than just queueing it...
When the source repo doesn't exist for a GHES-to-GHEC migration, the `migrate-repo` command currently fails with a not very helpful error: ``` System.Net.Http.HttpRequestException: Response status code does not indicate success:...
Before we start a migration, we should validate that the target personal access token (PAT) has the required scope(s) for the command being executed. This can be checked by comparing...
We saw an integration test fail with a 404 when trying to link the GH team to an AAD group. We've had alot of problems with apparant race conditions when...
As of #1057, we require `--bbs-server-url` to be provided for all variants of `bbs2gh migrate-repo` - even ones where we don't need to talk to the Bitbucket Server's API (i.e....
Currently `AdoClient` retries all failures for `GetAsync()` but `GetWithPagingAsync()` only retries on 503's. Ideally we would have `GetWithPagingAsync()` call `GetAsync()` so that the behavior matches. This would likely have fixed...
Currently, integration tests can only be run in GitHub Actions and are typically observed on push. We should update integration tests so that they easily and successfully run locally to...
We are constructing URLs by concatenating strings: https://github.com/github/gh-gei/blob/1740f9e74d06e12848eac9037f683fb6346e45e5/src/Octoshift/Services/AdoApi.cs#L30 It'd be better to use the `Uri` class to build URIs and consume them as `Uri` objects: - https://learn.microsoft.com/en-us/dotnet/api/system.uri?view=net-7.0 By using `Uri`...
TBD ## Todo - [ ] ... ## Dependencies - ...