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.

Assets 8

13 Dec 18:17

v0.5

generate-script with the --repos-only option no longer requires the Build scope on the ADO PAT

Assets 5

06 Dec 19:04

v0.4

Added descriptions to all commands in the built-in CLI help
add-team-to-repo now includes built-in help listing the valid values for the --role argument (octoshift add-team-to-repo --help), the CLI also validates the value of --role before attempting to run.
integrate-boards command now expects a single call per repo (instead of single call per team project with a list of repos). This will enable splitting a single team project into multiple batches for migration purposes. If no Boards-GitHub connection exists it will create it, otherwise it will add the repo to the existing connection. It assumes either 0 or 1 boards connection exists per team project (multiple connections in a single team project has not been tested).
migrate-repo now uses the GH_PAT for git push. The GH_PAT needs to have the repo scope in order for the git push to work.

Assets 5

05 Nov 05:04

v0.3

2x timestamped log files are generated on every run, timestamp.octoshift.log and timestamp.octoshift.verbose.log. A future release will include additional functionality to avoid the log file sprawl this may result in.
All commands support --verbose flag, this flag only controls what is output to the console. The verbose log file will always be created
Every API call will generate verbose output with the request and response contents

Assets 5