Jan 16
Loading video player...
Migrating from Azure DevOps to GitHub Actions? You already know CI/CD. You know pipelines, triggers, variables, stages. The syntax is just different enough to be annoying. This is your translation guide — same concepts, different YAML. What you'll learn: • File locations and basic workflow structure • Push triggers (trigger: vs on: push:) • Pull request triggers (pr: vs on: pull_request:) • The workflow_dispatch gotcha for manual runs • Variables and secrets syntax differences • Stages, jobs, and steps mapping • Conditions (condition: vs if:) • Templates vs reusable workflows • A cheat sheet you can screenshot Key insights: • If you know Azure DevOps pipelines, you're not starting from scratch • Variable syntax is the biggest adjustment: $(var) becomes ${{ env.VAR }} • GitHub Actions has no "stages" keyword — jobs are the top level • Manual runs require workflow_dispatch (unlike AzDO's always-available Run button) • Glob patterns differ: release/* in AzDO vs release/** in GitHub Whether you're actively migrating or just exploring GitHub Actions, this gets you productive fast. ► Full Playlist: https://www.youtube.com/playlist?list=PLGxFXI4dC2sio0QfqaDqO70H7BLXb_zvK Found this useful? Hit that like button! Subscribe for more GitHub Actions content for .NET teams. What's tripping you up in your migration? Tell me in the comments! #GitHubActions #AzureDevOps #CICD #DevOps #DotNet #YAML #GitHub #Migration #Pipeline #GitHubActionsForDotNet 0:00 Azure DevOps Pipelines vs GitHub Actions: A YAML Rosetta Stone 0:17 What We're Covering 0:39 It's the Same Concepts 0:54 File Location & Basic Structure 1:45 Push Triggers 2:38 Pull Request Triggers 3:25 Manual Triggers: The Hidden Gotcha 4:05 workflow_dispatch: Manual Runs in GitHub Actions 4:42 Variables 5:31 Secrets 6:14 Stages, Jobs, Steps 6:57 Conditions 7:47 Templates vs Reusable Workflows 8:26 Service Connections vs OIDC 9:02 ⚠️ Common Gotchas When Migrating 9:45 Quick Reference Table 10:13 Quick Recap 10:59 Thanks for Watching