Migration software
GitHub Actions Importer
Suggested in 2 of our migration playbooks, mainly for Servers and cloud. Here is what it handles, how it treats key settings, and other tools for the same jobs.
What it handles
The limits of the built-in tools that GitHub Actions Importer gets around, as covered in our playbooks.
Azure DevOps to GitHub migration
- Keep Boards and Pipelines for now, convert CI laterSecrets, service connections, unknown tasks and some triggers and gates still need manual work.
- GEI does not migrate pipelines.Converts Azure Pipelines to workflows. Secrets, service connections, unknown tasks and some triggers and gates still need manual work.
GitLab to GitHub migration
- Budget real effort for CI, it does not migrateMasked variable values and artifact reports still need manual work, and caching between jobs of different workflows is not supported.
- GEI does not move pipelines, CI/CD variables, job artifacts or pipeline triggers.Converts GitLab pipelines to workflows. Masked variables and artifact reports still need manual work, and caching between workflows is not supported.
How it handles key settings
From the settings checklists in our playbooks: what GitHub Actions Importer carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| Azure Pipelines | Converts Azure Pipelines to GitHub Actions workflows and opens a pull request. Secrets, service connections, unknown tasks and some triggers and gates still need manual work. | Azure DevOps to GitHub migration |
| CI/CD pipelines and variables | Converts GitLab pipelines to workflows and opens a pull request with them. Masked variable values and artifact reports need manual work, and caching between workflows is not supported. | GitLab to GitHub migration |
We write these notes from the vendor documentation cited in each playbook. Tools cannot pay to be included or to change them. Check the vendor's current documentation and terms before you buy.