Releases: github/gh-gei
Releases · github/gh-gei
v0.14
- Significant overhaul of how the
generate-script
command args work. Now by default it will generate a minimal script that only migrates the repos, and you will need to pass additional flags to script out additional automation (e.g.--rewire-pipelines
,--create-teams
, etc). The--all
flag will include all the automation in the script (the same as the previous version with no flags). - Updates most commands to be idempotent. They will check if there is anything to do, and if not they will print a message to that effect and complete successfully. E.g. create-team will check if the team already exists and if so exit as success (compared to previously where it would crash). The following commands have been updated:
- migrate-repo
- A generated script using
ado2gh
orgh gei
now include the CLI version that was used to generate it.
v0.13
- Compare the current running version against the latest version available on github.com and print out a message letting you know if you are up to date or not
- Add
reclaim-mannequin
command. Reclaims a mannequin, by sending a mannequin attribution invitation to the target user. If the mannequin has been previously mapped (and accepted) it will refuse to do so unless the--force
flag is set. - Sometimes
wait-for-migration
would error with a 502 error, now it will retry automatically when this happens - Sometimes
create-team
would error with a 404 error, now it will retry automatically when this happens
v0.12
- Add ado-team-project parameter to
ado2gh generate-script
command - Add ado-team-project parameter to
gh gei generate-script
command - All commands in both
ado2gh
andgei
now optionally accept required PATs as args as an alternate way to setting them as env variables.
v0.11
- Updating commands to be idempotent. They will check if there is anything to do, and if not they will print a message to that effect and complete successfully. E.g. create-team will check if the team already exists and if so exit as success (compared to previously where it would crash). The following commands have been updated:
- disable-ado-repo
- The change to automatically set the +x bit on the generated migration script has been rolled back (introduced in v0.10). We discovered a bug with this that caused
generate-script
to crash on MacOS. We're temporarily rolling this back to unblock customers while we investigate and fix the problem.
v0.10
- Add
wait-for-migration
command. It waits for the provided migration and returns as soon as it is complete. - Add
--wait
option tomigrate-repo
command. If set totrue
(default isfalse
) it will synchronously wait for the migration to finish, otherwise it will just queue up a repo migration and return themigration-id
. - Support parallel migrations with
generate-script
for bothado2gh
andgh gei
.generate-script
now by default generates a script to perform migrations in parallel. Adding--sequential
flag will force migrations to perform in a sequential (one by one) fashion. - Deprecate
--ssh
flag ingenerate-script
andmigrate-repo
commands for bothado2gh
andgh gei
. - Add powershell shebang command for execution of script on unix based systems.
- Add executable bit on generated scripts in unix based systems.
- Updates some commands to be idempotent. They will check if there is anything to do, and if not they will print a message to that effect and complete successfully. E.g. create-team will check if the team already exists and if so exit as success (compared to previously where it would crash). The following commands have been updated:
- configure-autolink
- create-team
v0.9
- Remove
gh gei generate-archive
- Update
gh gei migrate-repo
to allow for migrations from GHES instances. When--ghes-api-url
is passed in, it requires an Azure Blob Storage connection string--azure-storage-connection-string
and an optional flag to disable SSL verification--no-ssl-verify
. This migration path generates migration archives on the source, uploads them to Azure Blob Storage using the connection string, then kicks off a GitHub Enterprise Importer migration using the uploaded migration archives. - Modify
gh gei migrate-repo
to optionally accept two pre-generated archive urls to start a migration (not commonly used) and a target api url parameter - Fixed a bug where
configure-autolink
command would fail if your ADO team project had a space in it - Update
gh gei generate-script
to allow for migrations from GHES by passing the options--ghes-api-url
,--azure-storage-connection-string
,--no-ssl-verify
.
v0.8
- Adds the ability to migrate ADO repos using the
gh gei
CLI. This overlaps with some of the capabilities of ado2gh, but thegh gei
will not include all the extra ADO migration capabilities like re-wiring pipelines and boards integration.gh gei generate-script
now has an--ado-source-org
optiongh gei migrate-repo
now has--ado-source-org
and--ado-team-project
options
- Added
grant-migrator-role
andrevoke-migrator-role
commands togh gei
- Add gei command path for generating a migration archive
gh gei generate-archive
which uses the migration api on that instance to generate two archives of data, the metadata for a repository and the git data for that repository (this will primarily be useful for migrations from GHES) - The script generated from generate-script will now stop on the first command that fails. Previously this script could be renamed between .ps1 and .sh, but with this change it will now only work as a .ps1 script.
v0.7
Release Notes
- Do not log the error's stack trace to console in non-verberse mode.
- Show a generic error message instead of the actual one for unhandled exceptions in non-verbose mode.
- Exit code is now 1 instead of 0 in case of an error.
- Errors are written to std error instead of std out.
- Adding Support to get multi page results from Github API.
- The Github to Github migrations are no longer limited to 30 repos.
v0.6.1
Release Notes
- fixed bug where using --ssh flag would cause the migration to crash
v0.6
Release Notes
- Renamed the CLI from octoshift to ado2gh to indicate that this one is specifically for Azure DevOps -> GitHub migrations (in the future there will be additional CLI's for other migration scenarios)
- Released an extension for the official GitHub CLI that adds support for GitHub -> GitHub migrations (GHEC only for now). To install run:
gh extension install github/gh-gei
. To use run:gh gei --help
- Automatically remove secrets from log files and console output (previously the verbose logs would contain your PAT's)
- Added --ssh option to generate-script and migrate-repo commands (in both ado2gh and gh). This forces the migration to use an older version of the API's that uses SSH to push the repos into GitHub. The newer API's use HTTPS instead. However some customers have been running into problems with some repos that work fine using the older SSH API's. In the future this option will be deprecated once the issues with the HTTPS-based API's are resolved.