Acerca de las migraciones desde Azure DevOps
Puedes usar GitHub Enterprise Importer para migrar repositorios de Azure DevOps a GitHub Enterprise Cloud (GitHub.com o GHE.com).
Solo puedes usar GitHub Enterprise Importer para migrar desde Azure DevOps Cloud, no desde Azure DevOps Server. Si actualmente usas Azure DevOps Server y quieres realizar la migración a GitHub, puedes hacerlo primero a Azure DevOps Cloud. Para más información, consulta Migración a Azure DevOps en el sitio de Azure.
Datos que se migran
Actualmente solo se admite la migración de los siguientes datos de repositorio de Azure DevOps a GitHub Enterprise Cloud.
- Origen de Git (incluido el historial de confirmaciones)
- Solicitudes de incorporación de cambios
- Historial de usuarios para solicitudes de incorporación de cambios
- Vínculos de elementos de trabajo en solicitudes de incorporación de cambios
- Datos adjuntos en solicitudes de incorporación de cambios
- Directivas de rama para el repositorio (no se incluyen directivas de rama con ámbito de usuario ni directivas de rama entre repositorios)
Si quiere migrar Azure Pipelines a GitHub Actions, ponte en contacto con el administrador de cuentas de GitHub.
Limitaciones de los datos migrados
There are limits to what GitHub Enterprise Importer can migrate. Some are due to limitations of GitHub, while others are limitations of GitHub Enterprise Importer itself.
Limitations of GitHub
- 2 GB size limit for a single Git commit: No single commit in your Git repository can be larger than 2 GB. If any of your commits are larger than 2 GB, you will need to split the commit into smaller commits that are each 2 GB or smaller.
- 255 byte limit for Git references: No single Git reference, commonly known as a "ref", can have a name larger than 255 bytes. Usually, this means that your references cannot be more than 255 characters long, but any non-ASCII characters, such as emojis, may consume more than one byte. If any of your Git references are too large, we'll return a clear error message.
- 100 MB file size limit: After you complete your migration, no single file in your Git repository can be larger than 100 MB. During repository migration this limit is increased to 400 MB. Consider using Git LFS to store large files. For more information, see Administrar archivos grandes.
Limitaciones de GitHub Enterprise Importer
- 40 GB size limit for a Git repository (versión preliminar pública): This limit applies only to the source code. To check if the repository archive is over the limit, use the git-sizer tool and review the total blob size in the output. The git-sizer tool also helps to identify potential issues related to large files, blob size, commit size, and tree counts that could impact migrations.
- 400 MB file size limit: When migrating a repository with GitHub Enterprise Importer, no single file in your Git repository can be larger than 400 MB. Consider using Git LFS for storing large files. For more information, see Administrar archivos grandes.
- Git LFS objects not migrated: The Importer can migrate repositories that use Git LFS, but the LFS objects themselves will not be migrated. They can be pushed to your migration destination as a follow-up task after the migration is complete. For more information, see Duplicar un repositorio.
- Follow-up tasks required: When migrating between GitHub products, certain settings are not migrated and must be reconfigured in the new repository. For a list of follow-up tasks you'll need to complete after each migration, see Introducción a una migración entre productos de GitHub.
- Delayed code search functionality: Re-indexing the search index can take a few hours after a repository is migrated, and code searches may return unexpected results until re-indexing is complete.
- Rulesets configured for your organization can cause migrations to fail: For example, if you configured a rule that requires email addresses for commit authors to end with
@monalisa.cat, and the repository you're migrating contains commits that don't comply with this rule, your migration will fail. For more information about rulesets, see Acerca de los conjuntos de reglas. - Mannequin content might not be searchable: Mannequins are placeholder users to which imported content (such as issues, pull requests, comments, etc.) is associated. When you search for content associated with a mannequin, such as assigned issues, the issues may not be found. Once a mannequin is reclaimed, the content should be found via the new owner. For more information, see Reclamación de maniquíes para GitHub Enterprise Importer.
Introducción
Antes de migrar desde Azure DevOps, debe planear cómo ejecutará la migración. Antes de migrar los datos, deberá elegir a alguien para ejecutar la migración. Debe conceder a esa persona el acceso necesario para el origen y el destino de la migración. También le recomendamos ejecutar primero una migración de prueba.
Para obtener información general sobre el proceso de migración de principio a fin, consulta Introducción a una migración desde Azure DevOps a GitHub Enterprise Cloud.