gh-gei
gh-gei copied to clipboard
github
Migration CLI for GitHub to GitHub migrations
This PR adds support for migrating Dependabot alert dismissals in the GitHub Enterprise Importer (GEI), addressing the need to preserve dismissed Dependabot alerts and their dismissal reasons when migrating repositories....
## Problem The `ado2gh integrate-boards` command was incorrectly reporting success when it actually failed due to GitHub PAT permission issues. This occurred because the Azure DevOps API returns HTTP 200...
## Description We are investigating the possibility of migrating hundreds of Bitbucket cloud repos to Github. I saw that you have a bitbucket server importer, so I'm wondering why not...
If the GitHub PAT used has too many permissions the ADO API calls will fail (weird behavior I know). However, the GEI CLI will still report success incorrectly. Here is...
The `ado2gh integrate-boards` command requires an ADO Personal Access Token (PAT) with "All organizations" access selected, but this requirement was not clearly documented in the command's help text. This led...
After analyzing issue #1334, I found that the requested feature to include the original resolver name in migrated Secret Scanning alerts has already been implemented and is working correctly. ##...
## Description The GitHub Enterprise Importer (GEI) has been incrementally adding features to support the migration of Secret Scan Alert Resolutions, followed by Code Scan Alert Resolutions. ANZx has more...
## Description When using the `gh gei migrate-secret-alerts` to migrate alerts, the resolution comments from the source alert are also mapped over to the target alerts. Which works fine but...
## Description With the PR #1337 (that addresses #1334) we introduced a small bug when the new comment is longer then the allowed limit of the resolution comment of a...
Add a description to make it clearer that this option only works with Enterprise Managed Users. This is as per [migration friction 3294](https://github.com/github/migration-friction/issues/3294). - [ ] Did you write/update appropriate...
