Releases: github/gh-ado2gh
Releases · github/gh-ado2gh
v1.15.1
v1.15.0
- Improve resilience of
gh gei migrate-repo
andgh bb2gh migrate-repo
commands when uploading migration archives to GitHub owned storage.
v1.14.0
- Improved location matching logic for Secret Scanning alert locations in -
gh gei migrate-secret-alerts
. - Fixed a bug in
gh gei migrate-secret-alerts
where alerts with locations of noncommit
andwiki_commit
type were not matched correctly.
v1.13.0
gh gei migrate-repo
logs the git and metadata archive download paths when--keep-archive
is used.- Redact sensitive query arguments in SAS URLs
v1.12.0
- Update validation error messages for
gh bbs2gh migrate-repo
command when generating an archive is not required. gh gei migrate-code-scanning-alerts
now skips a not found code scanning analysis and continues with the rest.- Updated Secret Scanning Alerts migration (
gh gei migrate-secret-alerts
) command to match on all location types. Now includes: issues, pull requests.
v1.11.0
- Add progress report to
gh [gei|bbs2gh] migrate-repo
command when uploading migration archives to Azure Blob or AWS S3 gh gei migrate-repo
now allows using either--ghes-api-url
or archive paths (--git-archive-path
and--metadata-archive-path
).
v1.10.1
- catches exception when Target is not a member of the organization and the
--skip-invitation
flag is enabled
v1.10.0
- Adds
--git-archive-path
and--metadata-archive-path
options togh gei migrate-repo
for uploading (to selected storage) and migrating
v1.9.1
gh gei migrate-secret-alerts
copies the resolver name from the original alert to the resolution comment of the matching target alert. The comment follows this format:[@actorname] original comment
.
v1.9.0
- Add
--use-github-storage
togh [gei|bbs2gh] migrate-repo
command to support uploading to a GitHub owned storage - Add
--use-github-storage
togh [gei|bbs2gh] generate-script
command to support uploading to a GitHub owned storage