Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Answers
Import Data into GitHub
Import Repositories
Code itself, including branches, and commit history can be imported using the GitHub import tool. In Gitlab create a personal access with read only abilities and when prompted give the GitHub form your username and the GitLab token. Note: does not import non-core-git things like CI/CD setup.
Importing CI/CD
From Gitlab: Gitlab and GitHub use different syntax for structuring CI/CD pipelines, in GitHub called “actions ”. These are incompatible, and require the use of GitHub Action importer to translate or be re-written.
The GitHub Action Importer can read in CI/CD pipelines but it’s not perfect.
The importer requires an GitHub access token with write access to the repositories you want and your Gitlab token (read access only).
The setup can take some time but once setup it works. Unfortunately, it does not auto load secret keys values and they have to be manually created. Many of the repos use docker login to log into GitLab docker repository and build the project and to push them . This action, at least the pushing and receiving is here: https://github.com/docker/login-action and it may be worth to just rebuild the simpler ones instead of re-doing actions.
, multiple selections available,
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'ivy-ai' is unknown.