{"meta":{"title":"Migration à partir de Azure DevOps avec GitHub Actions Importer","intro":"Découvrez comment utiliser GitHub Actions Importer pour automatiser la migration de vos pipelines de Azure DevOps vers GitHub Actions.","product":"GitHub Actions","breadcrumbs":[{"href":"/fr/actions","title":"GitHub Actions"},{"href":"/fr/actions/tutorials","title":"Tutoriels"},{"href":"/fr/actions/tutorials/migrate-to-github-actions","title":"Migrer vers GitHub Actions"},{"href":"/fr/actions/tutorials/migrate-to-github-actions/automated-migrations","title":"Migrations automatisées"},{"href":"/fr/actions/tutorials/migrate-to-github-actions/automated-migrations/azure-devops-migration","title":"migration de Azure DevOps"}],"documentType":"article"},"body":"# Migration à partir de Azure DevOps avec GitHub Actions Importer\n\nDécouvrez comment utiliser GitHub Actions Importer pour automatiser la migration de vos pipelines de Azure DevOps vers GitHub Actions.\n\n\n## About migrating from Azure DevOps with GitHub Actions Importer\n\nThe instructions below will guide you through configuring your environment to use GitHub Actions Importer to migrate Azure DevOps pipelines to GitHub Actions.\n\n### Prerequisites\n\n* An Azure DevOps account or organization with projects and pipelines that you want to convert to GitHub Actions workflows.\n* Access to create an Azure DevOps 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 when migrating from Azure DevOps to GitHub Actions with GitHub Actions Importer:\n\n* GitHub Actions Importer requires version 5.0 of the Azure DevOps API, available in either Azure DevOps Services or Azure DevOps Server 2019. Older versions of Azure DevOps Server are not compatible.\n* Tasks that are implicitly added to an Azure DevOps pipeline, such as checking out source code, may be added to a GitHub Actions Importer audit as a GUID name. To find the friendly task name for a GUID, you can use the following URL: `https://dev.azure.com/:organization/_apis/distributedtask/tasks/:guid`.\n\n#### Manual tasks\n\nCertain Azure DevOps constructs must be migrated manually from Azure DevOps into GitHub Actions configurations. These include:\n\n* Organization, repository, and environment secrets\n* Service connections such as OIDC Connect, GitHub Apps, and personal access tokens\n* Unknown tasks\n* Self-hosted agents\n* Environments\n* Pre-deployment approvals\n\nFor more information on manual migrations, see [Migrating from Azure Pipelines to GitHub Actions](/en/actions/migrating-to-github-actions/manually-migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions).\n\n#### Unsupported tasks\n\nGitHub Actions Importer does not support migrating the following tasks:\n\n* Pre-deployment gates\n* Post-deployment gates\n* Post-deployment approvals\n* Some resource triggers\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 Azure DevOps 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 an Azure DevOps personal access token. For more information, see [Use personal access tokens](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops\\&tabs=Windows#create-a-pat) in the Azure DevOps documentation. The token must have the following scopes:\n\n * Agents Pool: `Read`\n * Build: `Read`\n * Code: `Read`\n * Release: `Read`\n * Service Connections: `Read`\n * Task Groups: `Read`\n * Variable Groups: `Read`\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 `Azure DevOps`, press Space to select it, then press Enter.\n * For \"Personal access token for GitHub\", enter the value of the personal access token (classic) that you created earlier, and press Enter.\n * For \"Base url of the GitHub instance\", press Enter to accept the default value (`https://github.com`).\n * For \"Personal access token for Azure DevOps\", enter the value for the Azure DevOps personal access token that you created earlier, and press Enter.\n * For \"Base url of the Azure DevOps instance\", press Enter to accept the default value (`https://dev.azure.com`).\n * For \"Azure DevOps organization name\", enter the name for your Azure DevOps organization, and press Enter.\n * For \"Azure DevOps project name\", enter the name for your Azure DevOps project, and press Enter.\n\n An example of the `configure` command is shown below:\n\n ```shell\n $ gh actions-importer configure\n ✔ Which CI providers are you configuring?: Azure DevOps\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 ✔ Personal access token for Azure DevOps: ***************\n ✔ Base url of the Azure DevOps instance: https://dev.azure.com\n ✔ Azure DevOps organization name: :organization\n ✔ Azure DevOps project name: :project\n Environment variables successfully updated.\n ```\n\n4. In your terminal, run the GitHub Actions Importer `update` CLI command to connect to the 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 Azure DevOps\n\nYou can use the `audit` command to get a high-level view of all projects in an Azure DevOps organization.\n\nThe `audit` command performs the following steps:\n\n1. Fetches all of the projects defined in an Azure DevOps organization.\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### Running the audit command\n\nTo perform an audit of an Azure DevOps organization, run the following command in your terminal:\n\n```shell\ngh actions-importer audit azure-devops --output-dir tmp/audit\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/security-guides/using-secrets-in-github-actions).\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 GitHub Actions usage\n\nYou can use the `forecast` command to forecast potential GitHub Actions usage by computing metrics from completed pipeline runs in Azure DevOps.\n\n### Running the forecast command\n\nTo perform a forecast of potential GitHub Actions usage, run the following command in your terminal. By default, GitHub Actions Importer includes the previous seven days in the forecast report.\n\n```shell\ngh actions-importer forecast azure-devops --output-dir tmp/forecast_reports\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\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 Azure DevOps. 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\n\nYou can use the `dry-run` command to convert an Azure DevOps 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\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/migrating-to-github-actions/automated-migrations/extending-github-actions-importer-with-custom-transformers).\n\n### Running the dry-run command for a build pipeline\n\nTo perform a dry run of migrating your Azure DevOps build pipeline to GitHub Actions, run the following command in your terminal, replacing `pipeline_id` with the ID of the pipeline you are converting.\n\n```shell\ngh actions-importer dry-run azure-devops pipeline --pipeline-id :pipeline_id --output-dir tmp/dry-run\n```\n\nYou can view the logs of the dry run and the converted workflow files in the specified output directory.\n\n### Running the dry-run command for a release pipeline\n\nTo perform a dry run of migrating your Azure DevOps release pipeline to GitHub Actions, run the following command in your terminal, replacing `pipeline_id` with the ID of the pipeline you are converting.\n\n```shell\ngh actions-importer dry-run azure-devops release --pipeline-id :pipeline_id --output-dir tmp/dry-run\n```\n\nYou can view the logs of the dry run and the converted workflow files in the specified output directory.\n\n## Perform a production migration\n\nYou can use the `migrate` command to convert an Azure DevOps pipeline and open a pull request with the equivalent GitHub Actions workflow.\n\n### Running the migrate command for a build pipeline\n\nTo migrate an Azure DevOps build pipeline to GitHub Actions, run the following command in your terminal, replacing the `target-url` value with the URL for your GitHub repository, and `pipeline_id` with the ID of the pipeline you are converting.\n\n```shell\ngh actions-importer migrate azure-devops pipeline --pipeline-id :pipeline_id --target-url https://github.com/octo-org/octo-repo --output-dir tmp/migrate\n```\n\nThe command's output includes the URL of 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 azure-devops pipeline --target-url https://github.com/octo-org/octo-repo --output-dir tmp/migrate --azure-devops-project my-azure-devops-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### Running the migrate command for a release pipeline\n\nTo migrate an Azure DevOps release pipeline to GitHub Actions, run the following command in your terminal, replacing the `target-url` value with the URL for your GitHub repository, and `pipeline_id` with the ID of the pipeline you are converting.\n\n```shell\ngh actions-importer migrate azure-devops release --pipeline-id :pipeline_id --target-url https://github.com/octo-org/octo-repo --output-dir tmp/migrate\n```\n\nThe command's output includes the URL of 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 azure-devops release --target-url https://github.com/octo-org/octo-repo --output-dir tmp/migrate --azure-devops-project my-azure-devops-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 Azure DevOps.\n\n### Configuration 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 Azure DevOps 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* `AZURE_DEVOPS_ACCESS_TOKEN`: The personal access token used to authenticate with your Azure DevOps instance. This token requires the following scopes:\n * Build: `Read`\n * Agent Pools: `Read`\n * Code: `Read`\n * Release: `Read`\n * Service Connections: `Read`\n * Task Groups: `Read`\n * Variable Groups: `Read`\n* `AZURE_DEVOPS_PROJECT`: The project name or GUID to use when migrating a pipeline. If you'd like to perform an audit on all projects, this is optional.\n* `AZURE_DEVOPS_ORGANIZATION`: The organization name of your Azure DevOps instance.\n* `AZURE_DEVOPS_INSTANCE_URL`: The URL to the Azure DevOps instance, such as `https://dev.azure.com`.\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### 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 azure-devops pipeline --output-dir ./output/ --source-file-path ./path/to/azure_devops/pipeline.yml\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 or composite action should be migrated to.\n\n##### Audit example\n\nIn this example, GitHub Actions Importer uses the specified YAML configuration file as the source file to perform an audit.\n\n```shell\ngh actions-importer audit azure-devops pipeline --output-dir ./output/ --config-file-path ./path/to/azure_devops/config.yml\n```\n\nTo audit an Azure DevOps instance using a configuration file, the configuration file must be in the following format and each `repository_slug` must be unique:\n\n```yaml\nsource_files:\n - repository_slug: azdo-project/1\n path: file.yml\n - repository_slug: azdo-project/2\n paths: path.yml\n```\n\nYou can generate the `repository_slug` for a pipeline by combining the Azure DevOps organization name, project name, and the pipeline ID. For example, `my-organization-name/my-project-name/42`.\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 `--azure-devops-organization` and `--azure-devops-project` option. The `path` is then used to pull the specified source file.\n\n```shell\ngh actions-importer dry-run azure-devops pipeline --output-dir ./output/ --config-file-path ./path/to/azure_devops/config.yml\n```\n\n##### Specify the repository of converted reusable workflows and composite actions\n\nGitHub Actions Importer uses the YAML file provided to the `--config-file-path` argument to determine the repository that converted reusable workflows and composite actions are migrated to.\n\nTo begin, you should run an audit without the `--config-file-path` argument:\n\n```shell\ngh actions-importer audit azure-devops --output-dir ./output/\n```\n\nThe output of this command will contain a file named `config.yml` that contains a list of all the reusable workflows and 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\ncomposite_actions:\n - name: my-composite-action.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 azure-devops pipeline --config-file-path config.yml --target-url https://github.com/my-org/my-repo\n```\n\n### Supported syntax for Azure DevOps pipelines\n\nThe following table shows the type of properties that GitHub Actions Importer is currently able to convert.\n\n| Azure Pipelines | GitHub Actions | Status |\n| :-------------------- | :----------------------------------------------------------------------------------------------------------------------------------------- | :------------------ |\n| condition | - `jobs..if`
- `jobs..steps[*].if`
| Supported |\n| container | - `jobs..container`
- `jobs..name`
| Supported |\n| continuousIntegration | | Supported |\n| job | | Supported |\n| pullRequest | | Supported |\n| stage | | Supported |\n| steps | | Supported |\n| strategy | - `jobs..strategy.fail-fast`
- `jobs..strategy.max-parallel`
- `jobs..strategy.matrix`
| Supported |\n| timeoutInMinutes | | Supported |\n| variables | - `env`
- `jobs..env`
- `jobs..steps.env`
| Supported |\n| manual deployment | | Partially supported |\n| pool | - `runners`
- `self hosted runners`
| Partially supported |\n| services | | Partially supported |\n| strategy | | Partially supported |\n| triggers | | Partially supported |\n| pullRequest | | Unsupported |\n| schedules | - `on.schedule`
- `on.workflow_run`
| Unsupported |\n| triggers | | Unsupported |\n\nFor more information about supported Azure DevOps tasks, see the [`github/gh-actions-importer` repository](https://github.com/github/gh-actions-importer/blob/main/docs/azure_devops/index.md).\n\n### Environment variable mapping\n\nGitHub Actions Importer uses the mapping in the table below to convert default Azure DevOps environment variables to the closest equivalent in GitHub Actions.\n\n| Azure Pipelines | GitHub Actions |\n| :------------------------------------------ | :-------------------------------------------------- |\n| `$(Agent.BuildDirectory)` | `${{ runner.workspace }}` |\n| `$(Agent.HomeDirectory)` | `${{ env.HOME }}` |\n| `$(Agent.JobName)` | `${{ github.job }}` |\n| `$(Agent.OS)` | `${{ runner.os }}` |\n| `$(Agent.ReleaseDirectory)` | `${{ github.workspace}}` |\n| `$(Agent.RootDirectory)` | `${{ github.workspace }}` |\n| `$(Agent.ToolsDirectory)` | `${{ runner.tool_cache }}` |\n| `$(Agent.WorkFolder)` | `${{ github.workspace }}` |\n| `$(Build.ArtifactStagingDirectory)` | `${{ runner.temp }}` |\n| `$(Build.BinariesDirectory)` | `${{ github.workspace }}` |\n| `$(Build.BuildId)` | `${{ github.run_id }}` |\n| `$(Build.BuildNumber)` | `${{ github.run_number }}` |\n| `$(Build.DefinitionId)` | `${{ github.workflow }}` |\n| `$(Build.DefinitionName)` | `${{ github.workflow }}` |\n| `$(Build.PullRequest.TargetBranch)` | `${{ github.base_ref }}` |\n| `$(Build.PullRequest.TargetBranch.Name)` | `${{ github.base_ref }}` |\n| `$(Build.QueuedBy)` | `${{ github.actor }}` |\n| `$(Build.Reason)` | `${{ github.event_name }}` |\n| `$(Build.Repository.LocalPath)` | `${{ github.workspace }}` |\n| `$(Build.Repository.Name)` | `${{ github.repository }}` |\n| `$(Build.Repository.Provider)` | `GitHub` |\n| `$(Build.Repository.Uri)` | `${{ github.server.url }}/${{ github.repository }}` |\n| `$(Build.RequestedFor)` | `${{ github.actor }}` |\n| `$(Build.SourceBranch)` | `${{ github.ref }}` |\n| `$(Build.SourceBranchName)` | `${{ github.ref }}` |\n| `$(Build.SourceVersion)` | `${{ github.sha }}` |\n| `$(Build.SourcesDirectory)` | `${{ github.workspace }}` |\n| `$(Build.StagingDirectory)` | `${{ runner.temp }}` |\n| `$(Pipeline.Workspace)` | `${{ runner.workspace }}` |\n| `$(Release.DefinitionEnvironmentId)` | `${{ github.job }}` |\n| `$(Release.DefinitionId)` | `${{ github.workflow }}` |\n| `$(Release.DefinitionName)` | `${{ github.workflow }}` |\n| `$(Release.Deployment.RequestedFor)` | `${{ github.actor }}` |\n| `$(Release.DeploymentID)` | `${{ github.run_id }}` |\n| `$(Release.EnvironmentId)` | `${{ github.job }}` |\n| `$(Release.EnvironmentName)` | `${{ github.job }}` |\n| `$(Release.Reason)` | `${{ github.event_name }}` |\n| `$(Release.RequestedFor)` | `${{ github.actor }}` |\n| `$(System.ArtifactsDirectory)` | `${{ github.workspace }}` |\n| `$(System.DefaultWorkingDirectory)` | `${{ github.workspace }}` |\n| `$(System.HostType)` | `build` |\n| `$(System.JobId)` | `${{ github.job }}` |\n| `$(System.JobName)` | `${{ github.job }}` |\n| `$(System.PullRequest.PullRequestId)` | `${{ github.event.number }}` |\n| `$(System.PullRequest.PullRequestNumber)` | `${{ github.event.number }}` |\n| `$(System.PullRequest.SourceBranch)` | `${{ github.ref }}` |\n| `$(System.PullRequest.SourceRepositoryUri)` | `${{ github.server.url }}/${{ github.repository }}` |\n| `$(System.PullRequest.TargetBranch)` | `${{ github.event.base.ref }}` |\n| `$(System.PullRequest.TargetBranchName)` | `${{ github.event.base.ref }}` |\n| `$(System.StageAttempt)` | `${{ github.run_number }}` |\n| `$(System.TeamFoundationCollectionUri)` | `${{ github.server.url }}/${{ github.repository }}` |\n| `$(System.WorkFolder)` | `${{ github.workspace }}` |\n\n### Templates\n\nYou can transform Azure DevOps templates with GitHub Actions Importer.\n\n#### Limitations\n\nGitHub Actions Importer is able to transform Azure DevOps templates with some limitations.\n\n* Azure DevOps templates used under the `stages`, `deployments`, and `jobs` keys are converted into reusable workflows in GitHub Actions. For more information, see [Reuse workflows](/en/actions/using-workflows/reusing-workflows).\n* Azure DevOps templates used under the `steps` key are converted into composite actions. For more information, see [Creating a composite action](/en/actions/creating-actions/creating-a-composite-action).\n* If you currently have job templates that reference other job templates, GitHub Actions Importer converts the templates into reusable workflows. Because reusable workflows cannot reference other reusable workflows, this is invalid syntax in GitHub Actions. You must manually correct nested reusable workflows.\n* If a template references an external Azure DevOps organization or GitHub repository, you must use the `--credentials-file` option to provide credentials to access this template. For more information, see [Supplemental arguments and settings](/en/actions/migrating-to-github-actions/automated-migrations/supplemental-arguments-and-settings#using-a-credentials-file-for-authentication).\n* You can dynamically generate YAML using `each` expressions with the following caveats:\n * Nested `each` blocks are not supported and cause the parent `each` block to be unsupported.\n * `each` and contained `if` conditions are evaluated at transformation time, because GitHub Actions does not support this style of insertion.\n * `elseif` blocks are unsupported. If this functionality is required, you must manually correct them.\n * Nested `if` blocks are supported, but `if/elseif/else` blocks nested under an `if` condition are not.\n * `if` blocks that use predefined Azure DevOps variables are not supported.\n\n#### Supported templates\n\nGitHub Actions Importer supports the templates listed in the table below.\n\n| Azure Pipelines | GitHub Actions | Status |\n| :------------------------------------------------------------------------- | :--------------------------- | ------------------: |\n| Extending from a template | `Reusable workflow` | Supported |\n| Job templates | `Reusable workflow` | Supported |\n| Stage templates | `Reusable workflow` | Supported |\n| Step templates | `Composite action` | Supported |\n| Task groups in classic editor | Varies | Supported |\n| Templates in a different Azure DevOps organization, project, or repository | Varies | Supported |\n| Templates in a GitHub repository | Varies | Supported |\n| Variable templates | `env` | Supported |\n| Conditional insertion | `if` conditions on job/steps | Partially supported |\n| Iterative insertion | Not applicable | Partially supported |\n| Templates with parameters | Varies | Partially supported |\n\n#### Template file path names\n\nGitHub Actions Importer can extract templates with relative or dynamic file paths with variable, parameter, and iterative expressions in the file name. However, there must be a default value set.\n\n##### Variable file path name example\n\n```yaml\n# File: azure-pipelines.yml\nvariables:\n- template: 'templates/vars.yml'\n\nsteps:\n- template: \"./templates/$\"\n```\n\n```yaml\n# File: templates/vars.yml\nvariables:\n one: 'simple_step.yml'\n```\n\n##### Parameter file path name example\n\n```yaml\nparameters:\n- name: template\n type: string\n default: simple_step.yml\n\nsteps:\n- template: \"./templates/${{ parameters.template }}\"\n```\n\n##### Iterative file path name example\n\n```yaml\nparameters:\n- name: steps\n type: object\n default:\n - build_step\n - release_step\nsteps:\n- ${{ each step in parameters.steps }}:\n - template: \"$-variables.yml\"\n```\n\n#### Template parameters\n\nGitHub Actions Importer supports the parameters listed in the table below.\n\n| Azure Pipelines | GitHub Actions | Status |\n| :-------------- | :----------------------------------------- | :------------------ |\n| string | `inputs.string` | Supported |\n| number | `inputs.number` | Supported |\n| boolean | `inputs.boolean` | Supported |\n| object | `inputs.string` with `fromJSON` expression | Partially supported |\n| step | `step` | Partially supported |\n| stepList | `step` | Partially supported |\n| job | `job` | Partially supported |\n| jobList | `job` | Partially supported |\n| deployment | `job` | Partially supported |\n| deploymentList | `job` | Partially supported |\n| stage | `job` | Partially supported |\n| stageList | `job` | Partially supported |\n\n> \\[!NOTE]\n> A template used under the `step` key with this parameter type is only serialized as a composite action if the steps are used at the beginning or end of the template steps. A template used under the `stage`, `deployment`, and `job` keys with this parameter type are not transformed into a reusable workflow, and instead are serialized as a standalone workflow.\n\n## Legal notice\n\nPortions have been adapted from 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```"}