{"meta":{"title":"Migrating from GitLab with GitHub Actions Importer","intro":"Learn how to use GitHub Actions Importer to automate the migration of your GitLab pipelines to GitHub Actions.","product":"GitHub Actions","breadcrumbs":[{"href":"/en/actions","title":"GitHub Actions"},{"href":"/en/actions/tutorials","title":"Tutorials"},{"href":"/en/actions/tutorials/migrate-to-github-actions","title":"Migrate to GitHub Actions"},{"href":"/en/actions/tutorials/migrate-to-github-actions/automated-migrations","title":"Automated migrations"},{"href":"/en/actions/tutorials/migrate-to-github-actions/automated-migrations/gitlab-migration","title":"GitLab migration"}],"documentType":"article"},"body":"# Migrating from GitLab with GitHub Actions Importer\n\nLearn how to use GitHub Actions Importer to automate the migration of your GitLab pipelines to GitHub Actions.\n\n## About migrating from GitLab with GitHub Actions Importer\n\nThe instructions below will guide you through configuring your environment to use GitHub Actions Importer to migrate GitLab pipelines to GitHub Actions.\n\n### Prerequisites\n\n* A GitLab account or organization with pipelines and jobs that you want to convert to GitHub Actions workflows.\n* Access to create a GitLab personal access token for your account or organization.\n* An environment where you can run Linux-based containers, and can install the necessary tools.\n  * Docker is [installed](https://docs.docker.com/get-docker/) and running.\n\n  * [GitHub CLI](https://cli.github.com) is installed.\n  > \\[!NOTE]\n  > The GitHub Actions Importer container and CLI do not need to be installed on the same server as your CI platform.\n\n### Limitations\n\nThere are some limitations on migrating processes automatically from GitLab pipelines to GitHub Actions with GitHub Actions Importer.\n\n* Automatic caching in between jobs of different workflows is not supported.\n* The `audit` command is only supported when using an organization account. However, the `dry-run` and `migrate` commands can be used with an organization or user account.\n\n#### Manual tasks\n\nCertain GitLab constructs must be migrated manually. These include:\n\n* Masked project or group variable values\n* Artifact reports\n\nFor more information on manual migrations, see [Migrating from GitLab CI/CD to GitHub Actions](/en/actions/tutorials/migrate-to-github-actions/manual-migrations/migrate-from-gitlab-cicd).\n\n## Installing the GitHub Actions Importer CLI extension\n\n1. Install the GitHub Actions Importer CLI extension:\n\n   ```bash copy\n   gh extension install github/gh-actions-importer\n   ```\n\n2. Verify that the extension is installed:\n\n   ```bash\n   $ gh actions-importer -h\n   Options:\n     -?, -h, --help  Show help and usage information\n\n   Commands:\n     update     Update to the latest version of GitHub Actions Importer.\n     version    Display the version of GitHub Actions Importer.\n     configure  Start an interactive prompt to configure credentials used to authenticate with your CI server(s).\n     audit      Plan your CI/CD migration by analyzing your current CI/CD footprint.\n     forecast   Forecast GitHub Actions usage from historical pipeline utilization.\n     dry-run    Convert a pipeline to a GitHub Actions workflow and output its yaml file.\n     migrate    Convert a pipeline to a GitHub Actions workflow and open a pull request with the changes.\n   ```\n\n## Configuring credentials\n\nThe `configure` CLI command is used to set required credentials and options for GitHub Actions Importer when working with GitLab and GitHub.\n\n1. Create a GitHub personal access token (classic). For more information, see [Managing your personal access tokens](/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-personal-access-token-classic).\n\n   Your token must have the `workflow` scope.\n\n   After creating the token, copy it and save it in a safe location for later use.\n\n2. Create a GitLab personal access token. For more information, see [Personal access tokens](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html#create-a-personal-access-token) in the GitLab documentation.\n\n   Your token must have the `read_api` scope.\n\n   After creating the token, copy it and save it in a safe location for later use.\n\n3. In your terminal, run the GitHub Actions Importer `configure` CLI command:\n\n   ```shell\n   gh actions-importer configure\n   ```\n\n   The `configure` command will prompt you for the following information:\n\n   * For \"Which CI providers are you configuring?\", use the arrow keys to select `GitLab`, press <kbd>Space</kbd> to select it, then press <kbd>Enter</kbd>.\n   * For \"Personal access token for GitHub\", enter the value of the personal access token (classic) that you created earlier, and press <kbd>Enter</kbd>.\n   * For \"Base url of the GitHub instance\", press <kbd>Enter</kbd> to accept the default value (`https://github.com`).\n   * For \"Private token for GitLab\", enter the value for the GitLab personal access token that you created earlier, and press <kbd>Enter</kbd>.\n   * For \"Base url of the GitLab instance\", enter the URL of your GitLab instance, and press <kbd>Enter</kbd>.\n\n   An example of the output of the `configure` command is shown below.\n\n   ```shell\n   $ gh actions-importer configure\n   ✔ Which CI providers are you configuring?: GitLab\n   Enter the following values (leave empty to omit):\n   ✔ Personal access token for GitHub: ***************\n   ✔ Base url of the GitHub instance: https://github.com\n   ✔ Private token for GitLab: ***************\n   ✔ Base url of the GitLab instance: http://localhost\n   Environment variables successfully updated.\n   ```\n\n4. In your terminal, run the GitHub Actions Importer `update` CLI command to connect to GitHub Packages Container registry and ensure that the container image is updated to the latest version:\n\n   ```shell\n   gh actions-importer update\n   ```\n\n   The output of the command should be similar to below:\n\n   ```shell\n   Updating ghcr.io/actions-importer/cli:latest...\n   ghcr.io/actions-importer/cli:latest up-to-date\n   ```\n\n## Perform an audit of GitLab\n\nYou can use the `audit` command to get a high-level view of all pipelines in a GitLab server.\n\nThe `audit` command performs the following steps:\n\n1. Fetches all of the projects defined in a GitLab server.\n2. Converts each pipeline to its equivalent GitHub Actions workflow.\n3. Generates a report that summarizes how complete and complex of a migration is possible with GitHub Actions Importer.\n\n### Prerequisites for the audit command\n\nIn order to use the `audit` command, you must have a personal access token configured with a GitLab organization account.\n\n### Running the audit command\n\nTo perform an audit of a GitLab server, run the following command in your terminal, replacing `my-gitlab-namespace` with the namespace or group you are auditing:\n\n```shell\ngh actions-importer audit gitlab --output-dir tmp/audit --namespace my-gitlab-namespace\n```\n\n### Inspecting the audit results\n\nThe files in the specified output directory contain the results of the audit. See the `audit_summary.md` file for a summary of the audit results.\n\nThe audit summary has the following sections.\n\n#### Pipelines\n\nThe \"Pipelines\" section contains a high-level statistics regarding the conversion rate done by GitHub Actions Importer.\n\nListed below are some key terms that can appear in the \"Pipelines\" section:\n\n* **Successful** pipelines had 100% of the pipeline constructs and individual items converted automatically to their GitHub Actions equivalent.\n* **Partially successful** pipelines had all of the pipeline constructs converted, however, there were some individual items that were not converted automatically to their GitHub Actions equivalent.\n* **Unsupported** pipelines are definition types that are not supported by GitHub Actions Importer.\n* **Failed** pipelines encountered a fatal error when being converted. This can occur for one of three reasons:\n  * The pipeline was originally misconfigured and not valid.\n  * GitHub Actions Importer encountered an internal error when converting it.\n  * There was an unsuccessful network response that caused the pipeline to be inaccessible, which is often due to invalid credentials.\n\n#### Build steps\n\nThe \"Build steps\" section contains an overview of individual build steps that are used across all pipelines, and how many were automatically converted by GitHub Actions Importer.\n\nListed below are some key terms that can appear in the \"Build steps\" section:\n\n* A **known** build step is a step that was automatically converted to an equivalent action.\n* An **unknown** build step is a step that was not automatically converted to an equivalent action.\n* An **unsupported** build step is a step that is either:\n  * Fundamentally not supported by GitHub Actions.\n  * Configured in a way that is incompatible with GitHub Actions.\n* An **action** is a list of the actions that were used in the converted workflows. This can be important for:\n  * If you use GitHub Enterprise Server, gathering the list of actions to sync to your instance.\n  * Defining an organization-level allowlist of actions that are used. This list of actions is a comprehensive list of actions that your security or compliance teams may need to review.\n\n#### Manual tasks\n\nThe \"Manual tasks\" section contains an overview of tasks that GitHub Actions Importer is not able to complete automatically, and that you must complete manually.\n\nListed below are some key terms that can appear in the \"Manual tasks\" section:\n\n* A **secret** is a repository or organization-level secret that is used in the converted pipelines. These secrets must be created manually in GitHub Actions for these pipelines to function properly. For more information, see [Using secrets in GitHub Actions](/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets).\n* A **self-hosted runner** refers to a label of a runner that is referenced in a converted pipeline that is not a GitHub-hosted runner. You will need to manually define these runners for these pipelines to function properly.\n\n#### Files\n\nThe final section of the audit report provides a manifest of all the files that were written to disk during the audit.\n\nEach pipeline file has a variety of files included in the audit, including:\n\n* The original pipeline as it was defined in GitHub.\n* Any network responses used to convert the pipeline.\n* The converted workflow file.\n* Stack traces that can be used to troubleshoot a failed pipeline conversion.\n\nAdditionally, the `workflow_usage.csv` file contains a comma-separated list of all actions, secrets, and runners that are used by each successfully converted pipeline. This can be useful for determining which workflows use which actions, secrets, or runners, and can be useful for performing security reviews.\n\n## Forecast potential build runner usage\n\nYou can use the `forecast` command to forecast potential GitHub Actions usage by computing metrics from completed pipeline runs in your GitLab server.\n\n### Running the forecast command\n\nTo perform a forecast of potential GitHub Actions usage, run the following command in your terminal, replacing `my-gitlab-namespace` with the namespace or group you are forecasting. By default, GitHub Actions Importer includes the previous seven days in the forecast report.\n\n```shell\ngh actions-importer forecast gitlab --output-dir tmp/forecast --namespace my-gitlab-namespace\n```\n\n### Forecasting an entire namespace\n\nTo forecast an entire namespace and all of its subgroups, you must specify each subgroup in the `--namespace` argument or `NAMESPACE` environment variable.\n\nFor example:\n\n```shell\ngh actions-importer forecast gitlab --namespace my-gitlab-namespace my-gitlab-namespace/subgroup-one my-gitlab-namespace/subgroup-two ...\n```\n\n### Inspecting the forecast report\n\nThe `forecast_report.md` file in the specified output directory contains the results of the forecast.\n\nListed below are some key terms that can appear in the forecast report:\n\n* The **job count** is the total number of completed jobs.\n* The **pipeline count** is the number of unique pipelines used.\n* **Execution time** describes the amount of time a runner spent on a job. This metric can be used to help plan for the cost of GitHub-hosted runners.\n  * This metric is correlated to how much you should expect to spend in GitHub Actions. This will vary depending on the hardware used for these minutes. You can use the [GitHub Actions pricing calculator](https://github.com/pricing/calculator) to estimate the costs.\n* **Queue time** metrics describe the amount of time a job spent waiting for a runner to be available to execute it.\n* **Concurrent jobs** metrics describe the amount of jobs running at any given time. This metric can be used to define the number of runners you should configure.\n\nAdditionally, these metrics are defined for each queue of runners in GitLab. This is especially useful if there is a mix of hosted or self-hosted runners, or high or low spec machines, so you can see metrics specific to different types of runners.\n\n## Perform a dry-run migration of a GitLab pipeline\n\nYou can use the `dry-run` command to convert a GitLab pipeline to its equivalent GitHub Actions workflow.\n\n### Running the dry-run command\n\nYou can use the `dry-run` command to convert a GitLab pipeline to an equivalent GitHub Actions workflow. A dry-run creates the output files in a specified directory, but does not open a pull request to migrate the pipeline.\n\nTo perform a dry run of migrating your GitLab pipelines to GitHub Actions, run the following command in your terminal, replacing `my-gitlab-project` with your GitLab project slug, and `my-gitlab-namespace` with the namespace or group (full group path for subgroups, e.g. `my-org/my-team`) you are performing a dry run for.\n\n```shell\ngh actions-importer dry-run gitlab --output-dir tmp/dry-run --namespace my-gitlab-namespace --project my-gitlab-project\n```\n\n### Inspecting the converted workflows\n\nYou can view the logs of the dry run and the converted workflow files in the specified output directory.\n\nIf there is anything that GitHub Actions Importer was not able to convert automatically, such as unknown build steps or a partially successful pipeline, you might want to create custom transformers to further customize the conversion process. For more information, see [Extending GitHub Actions Importer with custom transformers](/en/actions/reference/github-actions-importer/custom-transformers).\n\n## Perform a production migration of a GitLab pipeline\n\nYou can use the `migrate` command to convert a GitLab pipeline and open a pull request with the equivalent GitHub Actions workflow.\n\n### Running the migrate command\n\nTo migrate a GitLab pipeline to GitHub Actions, run the following command in your terminal, replacing the following values:\n\n* `target-url` value with the URL for your GitHub repository\n* `my-gitlab-project` with your GitLab project slug\n* `my-gitlab-namespace` with the namespace or group you are migrating (full path for subgroups, e.g. `my-org/my-team`)\n\n```shell\ngh actions-importer migrate gitlab --target-url https://github.com/:owner/:repo --output-dir tmp/migrate --namespace my-gitlab-namespace --project my-gitlab-project\n```\n\nThe command's output includes the URL to the pull request that adds the converted workflow to your repository. An example of a successful output is similar to the following:\n\n```shell\n$ gh actions-importer migrate gitlab --target-url https://github.com/octo-org/octo-repo --output-dir tmp/migrate --namespace octo-org --project monas-project\n[2022-08-20 22:08:20] Logs: 'tmp/migrate/log/actions-importer-20220916-014033.log'\n[2022-08-20 22:08:20] Pull request: 'https://github.com/octo-org/octo-repo/pull/1'\n```\n\n### Inspecting the pull request\n\nThe output from a successful run of the `migrate` command contains a link to the new pull request that adds the converted workflow to your repository.\n\nSome important elements of the pull request include:\n\n* In the pull request description, a section called **Manual steps**, which lists steps that you must manually complete before you can finish migrating your pipelines to GitHub Actions. For example, this section might tell you to create any secrets used in your workflows.\n* The converted workflows file. Select the **Files changed** tab in the pull request to view the workflow file that will be added to your GitHub repository.\n\nWhen you are finished inspecting the pull request, you can merge it to add the workflow to your GitHub repository.\n\n## Reference\n\nThis section contains reference information on environment variables, optional arguments, and supported syntax when using GitHub Actions Importer to migrate from GitLab.\n\n### Using environment variables\n\nGitHub Actions Importer uses environment variables for its authentication configuration. These variables are set when following the configuration process using the `configure` command. For more information, see the [Configuring credentials](#configuring-credentials) section.\n\nGitHub Actions Importer uses the following environment variables to connect to your GitLab instance:\n\n* `GITHUB_ACCESS_TOKEN`: The personal access token (classic) used to create pull requests with a converted workflow (requires the `workflow` scope).\n* `GITHUB_INSTANCE_URL`: The URL to the target GitHub instance (for example, `https://github.com`).\n* `GITLAB_ACCESS_TOKEN`: The GitLab personal access token used to view GitLab resources.\n* `GITLAB_INSTANCE_URL`: The URL of the GitLab instance.\n* `NAMESPACE`: The namespaces or groups that contain the GitLab pipelines.\n\nThese environment variables can be specified in a `.env.local` file that is loaded by GitHub Actions Importer when it is run.\n\n### Using optional arguments\n\nThere are optional arguments you can use with the GitHub Actions Importer subcommands to customize your migration.\n\n#### `--source-file-path`\n\nYou can use the `--source-file-path` argument with the `forecast`, `dry-run`, or `migrate` subcommands.\n\nBy default, GitHub Actions Importer fetches pipeline contents from source control. The `--source-file-path` argument tells GitHub Actions Importer to use the specified source file path instead.\n\nFor example:\n\n```shell\ngh actions-importer dry-run gitlab --output-dir output/ --namespace my-gitlab-namespace --project my-gitlab-project --source-file-path path/to/.gitlab-ci.yml\n```\n\nIf you would like to supply multiple source files when running the `forecast` subcommand, you can use pattern matching in the file path value. The following example supplies GitHub Actions Importer with any source files that match the `./tmp/previous_forecast/jobs/*.json` file path.\n\n```shell\ngh actions-importer forecast gitlab --output-dir output/ --namespace my-gitlab-namespace --project my-gitlab-project --source-file-path ./tmp/previous_forecast/jobs/*.json\n```\n\n#### `--config-file-path`\n\nYou can use the `--config-file-path` argument with the `audit`, `dry-run`, and `migrate` subcommands.\n\nBy default, GitHub Actions Importer fetches pipeline contents from source control. The `--config-file-path` argument tells GitHub Actions Importer to use the specified source files instead.\n\nThe `--config-file-path` argument can also be used to specify which repository a converted reusable workflow should be migrated to.\n\n##### Audit example\n\nIn this example, GitHub Actions Importer uses the specified YAML configuration file to perform an audit.\n\n```shell\ngh actions-importer audit gitlab --output-dir path/to/output/ --namespace my-gitlab-namespace --config-file-path path/to/gitlab/config.yml\n```\n\nTo audit a GitLab instance using a configuration file, the file must be in the following format, and each `repository_slug` value must be unique:\n\n```yaml\nsource_files:\n  - repository_slug: namespace/project-name\n    path: path/to/.gitlab-ci.yml\n  - repository_slug: namespace/some-other-project-name\n    path: path/to/.gitlab-ci.yml\n```\n\n##### Dry run example\n\nIn this example, GitHub Actions Importer uses the specified YAML configuration file as the source file to perform a dry run.\n\nThe pipeline is selected by matching the `repository_slug` in the configuration file to the value of the `--namespace` and `--project` options. The `path` is then used to pull the specified source file.\n\n```shell\ngh actions-importer dry-run gitlab --namespace my-gitlab-namespace --project my-gitlab-project-name --output-dir ./output/ --config-file-path ./path/to/gitlab/config.yml\n```\n\n##### Specify the repository of converted reusable workflows\n\nGitHub Actions Importer uses the YAML file provided to the `--config-file-path` argument to determine the repository that converted reusable workflows are migrated to.\n\nTo begin, you should run an audit without the `--config-file-path` argument:\n\n```shell\ngh actions-importer audit gitlab --output-dir ./output/\n```\n\nThe output of this command will contain a file named `config.yml` that contains a list of all the composite actions that were converted by GitHub Actions Importer. For example, the `config.yml` file may have the following contents:\n\n```yaml\nreusable_workflows:\n  - name: my-reusable-workflow.yml\n    target_url: https://github.com/octo-org/octo-repo\n    ref: main\n```\n\nYou can use this file to specify which repository and ref a reusable workflow or composite action should be added to. You can then use the `--config-file-path` argument to provide the `config.yml` file to GitHub Actions Importer. For example, you can use this file when running a `migrate` command to open a pull request for each unique repository defined in the config file:\n\n```shell\ngh actions-importer migrate gitlab --project my-project-name --output-dir output/ --config-file-path config.yml --target-url https://github.com/my-org/my-repo\n```\n\n### Supported syntax for GitLab pipelines\n\nThe following table shows the type of properties GitHub Actions Importer is currently able to convert. For more details about how GitLab pipeline syntax aligns with GitHub Actions, see [Migrating from GitLab CI/CD to GitHub Actions](/en/actions/tutorials/migrate-to-github-actions/manual-migrations/migrate-from-gitlab-cicd).\n\n| GitLab Pipelines                        | GitHub Actions                                                                                          | Status              |\n| :-------------------------------------- | :------------------------------------------------------------------------------------------------------ | :------------------ |\n| `after_script`                          | `jobs.<job_id>.steps`                                                                                   | Supported           |\n| `auto_cancel_pending_pipelines`         | `concurrency`                                                                                           | Supported           |\n| `before_script`                         | `jobs.<job_id>.steps`                                                                                   | Supported           |\n| `build_timeout` or `timeout`            | `jobs.<job_id>.timeout-minutes`                                                                         | Supported           |\n| `default`                               | Not applicable                                                                                          | Supported           |\n| `image`                                 | `jobs.<job_id>.container`                                                                               | Supported           |\n| `job`                                   | `jobs.<job_id>`                                                                                         | Supported           |\n| `needs`                                 | `jobs.<job_id>.needs`                                                                                   | Supported           |\n| `only_allow_merge_if_pipeline_succeeds` | `on.pull_request`                                                                                       | Supported           |\n| `resource_group`                        | `jobs.<job_id>.concurrency`                                                                             | Supported           |\n| `schedule`                              | `on.schedule`                                                                                           | Supported           |\n| `script`                                | `jobs.<job_id>.steps`                                                                                   | Supported           |\n| `stages`                                | `jobs`                                                                                                  | Supported           |\n| `tags`                                  | `jobs.<job_id>.runs-on`                                                                                 | Supported           |\n| `variables`                             | `env`, `jobs.<job_id>.env`                                                                              | Supported           |\n| Run pipelines for new commits           | `on.push`                                                                                               | Supported           |\n| Run pipelines manually                  | `on.workflow_dispatch`                                                                                  | Supported           |\n| `environment`                           | `jobs.<job_id>.environment`                                                                             | Partially supported |\n| `include`                               | Files referenced in an `include` statement are merged into a single job graph before being transformed. | Partially supported |\n| `only` or `except`                      | `jobs.<job_id>.if`                                                                                      | Partially supported |\n| `parallel`                              | `jobs.<job_id>.strategy`                                                                                | Partially supported |\n| `rules`                                 | `jobs.<job_id>.if`                                                                                      | Partially supported |\n| `services`                              | `jobs.<job_id>.services`                                                                                | Partially supported |\n| `workflow`                              | `if`                                                                                                    | Partially supported |\n\nFor information about supported GitLab constructs, see the [`github/gh-actions-importer` repository](https://github.com/github/gh-actions-importer/blob/main/docs/gitlab/index.md).\n\n### Environment variables syntax\n\nGitHub Actions Importer uses the mapping in the table below to convert default GitLab environment variables to the closest equivalent in GitHub Actions.\n\n| GitLab                                        | GitHub Actions                                                                        |\n| :-------------------------------------------- | :------------------------------------------------------------------------------------ |\n| `CI_API_V4_URL`                               | `${{ github.api_url }}`                                                               |\n| `CI_BUILDS_DIR`                               | `${{ github.workspace }}`                                                             |\n| `CI_COMMIT_BRANCH`                            | `${{ github.ref }}`                                                                   |\n| `CI_COMMIT_REF_NAME`                          | `${{ github.ref }}`                                                                   |\n| `CI_COMMIT_REF_SLUG`                          | `${{ github.ref }}`                                                                   |\n| `CI_COMMIT_SHA`                               | `${{ github.sha }}`                                                                   |\n| `CI_COMMIT_SHORT_SHA`                         | `${{ github.sha }}`                                                                   |\n| `CI_COMMIT_TAG`                               | `${{ github.ref }}`                                                                   |\n| `CI_JOB_ID`                                   | `${{ github.job }}`                                                                   |\n| `CI_JOB_MANUAL`                               | `${{ github.event_name == 'workflow_dispatch' }}`                                     |\n| `CI_JOB_NAME`                                 | `${{ github.job }}`                                                                   |\n| `CI_JOB_STATUS`                               | `${{ job.status }}`                                                                   |\n| `CI_JOB_URL`                                  | `${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}` |\n| `CI_JOB_TOKEN`                                | `${{ github.token }}`                                                                 |\n| `CI_NODE_INDEX`                               | `${{ strategy.job-index }}`                                                           |\n| `CI_NODE_TOTAL`                               | `${{ strategy.job-total }}`                                                           |\n| `CI_PIPELINE_ID`                              | `${{ github.repository}}/${{ github.workflow }}`                                      |\n| `CI_PIPELINE_IID`                             | `${{ github.workflow }}`                                                              |\n| `CI_PIPELINE_SOURCE`                          | `${{ github.event_name }}`                                                            |\n| `CI_PIPELINE_TRIGGERED`                       | `${{ github.actions }}`                                                               |\n| `CI_PIPELINE_URL`                             | `${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}` |\n| `CI_PROJECT_DIR`                              | `${{ github.workspace }}`                                                             |\n| `CI_PROJECT_ID`                               | `${{ github.repository }}`                                                            |\n| `CI_PROJECT_NAME`                             | `${{ github.event.repository.name }}`                                                 |\n| `CI_PROJECT_NAMESPACE`                        | `${{ github.repository_owner }}`                                                      |\n| `CI_PROJECT_PATH_SLUG`                        | `${{ github.repository }}`                                                            |\n| `CI_PROJECT_PATH`                             | `${{ github.repository }}`                                                            |\n| `CI_PROJECT_ROOT_NAMESPACE`                   | `${{ github.repository_owner }}`                                                      |\n| `CI_PROJECT_TITLE`                            | `${{ github.event.repository.full_name }}`                                            |\n| `CI_PROJECT_URL`                              | `${{ github.server_url }}/${{ github.repository }}`                                   |\n| `CI_REPOSITORY_URL`                           | `${{ github.event.repository.clone_url }}`                                            |\n| `CI_RUNNER_EXECUTABLE_ARCH`                   | `${{ runner.os }}`                                                                    |\n| `CI_SERVER_HOST`                              | `${{ github.server_url }}`                                                            |\n| `CI_SERVER_URL`                               | `${{ github.server_url }}`                                                            |\n| `CI_SERVER`                                   | `${{ github.actions }}`                                                               |\n| `GITLAB_CI`                                   | `${{ github.actions }}`                                                               |\n| `GITLAB_USER_EMAIL`                           | `${{ github.actor }}`                                                                 |\n| `GITLAB_USER_ID`                              | `${{ github.actor }}`                                                                 |\n| `GITLAB_USER_LOGIN`                           | `${{ github.actor }}`                                                                 |\n| `GITLAB_USER_NAME`                            | `${{ github.actor }}`                                                                 |\n| `TRIGGER_PAYLOAD`                             | `${{ github.event_path }}`                                                            |\n| `CI_MERGE_REQUEST_ASSIGNEES`                  | `${{ github.event.pull_request.assignees }}`                                          |\n| `CI_MERGE_REQUEST_ID`                         | `${{ github.event.pull_request.number }}`                                             |\n| `CI_MERGE_REQUEST_IID`                        | `${{ github.event.pull_request.number }}`                                             |\n| `CI_MERGE_REQUEST_LABELS`                     | `${{ github.event.pull_request.labels }}`                                             |\n| `CI_MERGE_REQUEST_MILESTONE`                  | `${{ github.event.pull_request.milestone }}`                                          |\n| `CI_MERGE_REQUEST_PROJECT_ID`                 | `${{ github.repository }}`                                                            |\n| `CI_MERGE_REQUEST_PROJECT_PATH`               | `${{ github.repository }}`                                                            |\n| `CI_MERGE_REQUEST_PROJECT_URL`                | `${{ github.server_url }}/${{ github.repository }}`                                   |\n| `CI_MERGE_REQUEST_REF_PATH`                   | `${{ github.ref }}`                                                                   |\n| `CI_MERGE_REQUEST_SOURCE_BRANCH_NAME`         | `${{ github.event.pull_request.head.ref }}`                                           |\n| `CI_MERGE_REQUEST_SOURCE_BRANCH_SHA`          | `${{ github.event.pull_request.head.sha}}`                                            |\n| `CI_MERGE_REQUEST_SOURCE_PROJECT_ID`          | `${{ github.event.pull_request.head.repo.full_name }}`                                |\n| `CI_MERGE_REQUEST_SOURCE_PROJECT_PATH`        | `${{ github.event.pull_request.head.repo.full_name }}`                                |\n| `CI_MERGE_REQUEST_SOURCE_PROJECT_URL`         | `${{ github.event.pull_request.head.repo.url }}`                                      |\n| `CI_MERGE_REQUEST_TARGET_BRANCH_NAME`         | `${{ github.event.pull_request.base.ref }}`                                           |\n| `CI_MERGE_REQUEST_TARGET_BRANCH_SHA`          | `${{ github.event.pull_request.base.sha }}`                                           |\n| `CI_MERGE_REQUEST_TITLE`                      | `${{ github.event.pull_request.title }}`                                              |\n| `CI_EXTERNAL_PULL_REQUEST_IID`                | `${{ github.event.pull_request.number }}`                                             |\n| `CI_EXTERNAL_PULL_REQUEST_SOURCE_REPOSITORY`  | `${{ github.event.pull_request.head.repo.full_name }}`                                |\n| `CI_EXTERNAL_PULL_REQUEST_TARGET_REPOSITORY`  | `${{ github.event.pull_request.base.repo.full_name }}`                                |\n| `CI_EXTERNAL_PULL_REQUEST_SOURCE_BRANCH_NAME` | `${{ github.event.pull_request.head.ref }}`                                           |\n| `CI_EXTERNAL_PULL_REQUEST_SOURCE_BRANCH_SHA`  | `${{ github.event.pull_request.head.sha }}`                                           |\n| `CI_EXTERNAL_PULL_REQUEST_TARGET_BRANCH_NAME` | `${{ github.event.pull_request.base.ref }}`                                           |\n| `CI_EXTERNAL_PULL_REQUEST_TARGET_BRANCH_SHA`  | `${{ github.event.pull_request.base.sha }}`                                           |\n\n## Legal notice\n\nPortions have been adapted from <https://github.com/github/gh-actions-importer/> under the MIT license:\n\n```text\nMIT License\n\nCopyright (c) 2022 GitHub\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n```"}