Answers: <p>Different between Azure DevOps versus GitHub Actions:</p>
  <ol>
  <li><p>Azure Pipelines supports a legacy classic editor, which lets you define your CI configuration in a GUI editor instead of creating the pipeline definition in a YAML file. GitHub Actions uses YAML files to define workflows and does not support a graphical editor.</p>
  </li>
  <li><p>Azure Pipelines allows you to omit some structure in job definitions. For example, if you only have a single job, you don't need to define the job and only need to define its steps. GitHub Actions requires explicit configuration, and YAML structure cannot be omitted.</p>
  </li>
  <li><p>Azure Pipelines supports stages defined in the YAML file, which can be used to create deployment workflows. GitHub Actions requires you to separate stages into separate YAML workflow files.</p>
  </li>
  <li><p>On-premises Azure Pipelines build agents can be selected with capabilities. GitHub Actions self-hosted runners can be selected with labels.</p>
  </li>
  </ol>
  <p>Source <a href="https://docs.github.com/en/actions/migrating-to-github-actions/manually-migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions#key-differences" rel="nofollow noreferrer">https://docs.github.com/en/actions/migrating-to-github-actions/manually-migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions#key-differences</a></p>
  
Answers: CC BY-SA 4.0
Answers: 2024-01-26T07:30:54.317Z
Answers: 2024-01-26T07:30:54.317Z
Answers: Vy Do
Body: <p>My team is thinking of switching from Azure DevOps to GitHub Actions, currently we are using Azure DevOps Pipelines to handle code deployments. Our release pipelines are configured in a way where they are multi-staged whereas each stage is an environment (dev,qa,prod) and we also have a &quot;review stage/approval&quot; in the pipeline where someone has to review the code in the github repo before approving it. Also we will soon have some pipelines that will source from multiple repos. Will GitHub actions even support something like this? What are the main differences between Azure DevOps/Piplines and GitHub Actions? I heard github actions can only be pointed (or sourced) from a single repo.<a href="https://i.sstatic.net/jOq57.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/jOq57.png" alt="enter image description here" /></a></p>
  
Tags: <azure-devops><azure-pipelines><cicd><github><github-actions>
Title: What are the differences between Azure DevOps (Pipelines) and GitHub Actions?
UserDisplayName: Eric Swiggum
ThreadText: # What are the differences between Azure DevOps (Pipelines) and GitHub Actions?
  
  (Asked by: username_0 on 2023-10-30)
  
  My team is thinking of switching from Azure DevOps to GitHub Actions, currently we are using Azure DevOps Pipelines to handle code deployments. Our release pipelines are configured in a way where they are multi-staged whereas each stage is an environment (dev,qa,prod) and we also have a "review stage/approval" in the pipeline where someone has to review the code in the github repo before approving it. Also we will soon have some pipelines that will source from multiple repos. Will GitHub actions even support something like this? What are the main differences between Azure DevOps/Piplines and GitHub Actions? I heard github actions can only be pointed (or sourced) from a single repo.[![enter image description here](https://i.sstatic.net/jOq57.png)](https://i.sstatic.net/jOq57.png)
  
  **Tags:** azure-devops, azure-pipelines, cicd, github, github-actions
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2024-01-26. Score: 2
  
  Different between Azure DevOps versus GitHub Actions:
  
  1. Azure Pipelines supports a legacy classic editor, which lets you define your CI configuration in a GUI editor instead of creating the pipeline definition in a YAML file. GitHub Actions uses YAML files to define workflows and does not support a graphical editor.
  2. Azure Pipelines allows you to omit some structure in job definitions. For example, if you only have a single job, you don't need to define the job and only need to define its steps. GitHub Actions requires explicit configuration, and YAML structure cannot be omitted.
  3. Azure Pipelines supports stages defined in the YAML file, which can be used to create deployment workflows. GitHub Actions requires you to separate stages into separate YAML workflow files.
  4. On-premises Azure Pipelines build agents can be selected with capabilities. GitHub Actions self-hosted runners can be selected with labels.
  
  Source <https://docs.github.com/en/actions/migrating-to-github-actions/manually-migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions#key-differences>
  
  
  ---
  
  