GitHub Actions Certification

GH-200 · ● Active · Associate · GitHub (Microsoft)

Certification Landscape Note: GitHub does not formally issue a "GitHub Certified Developer" cert. The GH-200 (GitHub Actions) is the closest Associate-level equivalent for developers and engineers validating CI/CD and workflow automation expertise on GitHub's platform. GitHub offers five certifications: GH-900 (Foundations, entry-level), GH-100 (Administration, enterprise focus), GH-200 (Actions, this cert), GH-300 (Copilot, AI-assisted dev), and GH-500 (Advanced Security). The GH-200 is the most directly applicable to developers building and maintaining CI/CD pipelines.

Exam facts

Vendor source — GitHub Actions Certification ↗

Official exam guide — Study Guide: Exam GH-200 ↗

Exam registration — Register via Pearson VUE ↗

About

The GitHub Actions Certification (GH-200) validates intermediate to advanced competency in automating software development workflows using GitHub Actions — the native CI/CD orchestration and workflow automation platform for GitHub. Launched in 2023 and substantially updated in January 2026, it targets DevOps engineers, software developers, platform engineers, and release engineers who design, maintain, and scale automation across GitHub repositories and enterprises.

GitHub Actions is tightly integrated into the GitHub platform, running directly within the context of GitHub repositories without requiring external CI/CD tools. This deep integration allows teams to author, trigger, and monitor CI/CD pipelines without leaving their code review workflow. Unlike standalone CI/CD platforms (Jenkins, CircleCI, GitLab CI), GitHub Actions reduces configuration overhead and decision paralysis for teams already standardized on GitHub.

The certification validates core competencies including YAML workflow authoring, self-hosted runner management at scale, secure secrets handling via OpenID Connect (OIDC), third-party service integration (AWS, Azure, Docker Hub, npm registries), and architecture of CI/CD systems for multi-team GitHub Enterprise environments. The exam was significantly updated in January 2026, with new objectives around enterprise runner management, advanced security practices, and passwordless deployments, making it current for modern DevOps workflows.

Domain context — DevOps / CI/CD

The DevOps / CI-CD domain spans version control orchestration and continuous integration/continuous deployment (CI/CD) pipeline automation — the glue between code and production. DevOps professionals in this domain bridge development (rapid iteration, feature velocity) and operations (stability, compliance, scalability) using automation, infrastructure-as-code, and monitoring.

GitHub Actions is the native CI/CD engine for GitHub and github.com, integrated directly into pull request workflows, branch protection rules, and deployment gates. Unlike standalone platforms (Jenkins, CircleCI, GitLab CI), GitHub Actions runs within GitHub's runner infrastructure, reducing operational overhead for teams already on the GitHub platform. The GH-200 validates GitHub-specific CI/CD orchestration; cross-vendor CI/CD skills are tested in other certifications.

This domain encompasses workflow automation platforms (GitHub Actions, GitLab CI/CD, Jenkins, CircleCI), container runtimes and orchestration (Docker, Kubernetes CKA/CKAD), infrastructure-as-code (Terraform, CloudFormation, Ansible), deployment automation (Helm, ArgoCD), and observability/monitoring for CI/CD pipelines. The DevOps/CI-CD domain overlaps with Cloud (AWS Lambda, Azure Functions, GCP Cloud Run deployments), Security (secrets management, compliance scanning, OIDC), and Platform Engineering (self-service infrastructure).

Related domains: Cloud Platforms · Kubernetes · Security & Compliance · Platform Engineering

Read full ecosystem deep dive — GitHub Ecosystem → (file not yet created)

Topics covered

Based on the official Microsoft Learn exam guide (updated January 2026), the GH-200 exam covers the following five functional domains, each weighted by exam importance:

1. Author and manage workflows (20–25% weight)

• Create and configure workflow files (.github/workflows/*.yml)
• YAML syntax, indentation rules, and common errors
• Workflow triggers: push, pull_request, schedule (cron), workflow_dispatch, workflow_call, webhook events
• Event filtering: branches, tags, paths, pull request types
• Conditional execution: if conditions, job success/failure evaluation
• Reusable workflows and composite actions (calling shared workflows across repos)
• Workflow visualization and debugging via GitHub UI logs
• Example: Creating a pull request workflow that runs linting and tests on every PR to main branch

2. Manage GitHub Actions for the enterprise (15–20% weight)

• Self-hosted runner setup and configuration (Ubuntu, macOS, Windows, Docker)
• Runner groups and assignment policies (organization-level or repository-level)
• Enterprise-scale runner architecture and scaling strategies
• Security hardening and isolation (network, process, credential handling)
• Resource management (CPU, memory, disk limits; concurrent job limits)
• Runner monitoring, troubleshooting, and observability
• GitHub Enterprise Server (GHES) runner considerations
• Example: Scaling a fleet of self-hosted runners behind a reverse proxy for on-premises deployments

3. Consume GitHub Actions and customize workflows (20–25% weight)

• Using pre-built actions from GitHub Marketplace (checkout, upload-artifact, deploy-to-production)
• Referencing actions by version tag or commit SHA
• Passing inputs and outputs between actions
• Docker container actions (using docker:// image reference)
• JavaScript/TypeScript actions (using Node.js runtime)
• Composite actions (bundling shell scripts and other actions into a reusable unit)
• Setting environment variables and using contexts (github, runner, env, secrets, vars, inputs, matrix, needs)
• Example: Using aws-actions/configure-aws-credentials and aws-actions/cloudformation-action-helper for deployment

4. Manage runners and enable secure workflows (15–20% weight)

• OIDC (OpenID Connect) federation for passwordless cloud deployments (AWS STS, Azure Workload Identity, Google Cloud Workload Identity)
• Secrets management: repository secrets, environment secrets, organization secrets; encryption at rest
• Preventing secrets leakage in logs and artifacts
• Matrix builds and job parallelization (test across multiple Node versions, OS platforms)
• Job dependencies (needs keyword)
• Conditional execution and status checks (pass/fail gates on deployments)
• Example: Deploying to AWS Lambda without storing AWS credentials in secrets, using OIDC token exchange

5. Author and maintain actions (10–15% weight)

• Developing Docker-based custom actions (Dockerfile, entrypoint)
• Developing JavaScript/TypeScript actions (action.yml metadata, Node.js handler)
• Developing composite actions (reusable wrapper around shell/run/action steps)
• Action metadata (action.yml): inputs, outputs, runs, branding
• Versioning and releasing actions (GitHub releases, major/minor tags)
• Testing custom actions before publication
• Publishing actions to GitHub Marketplace
• Example: Creating a custom Slack notifier action that posts workflow results to Slack

Source: Official Study Guide for Exam GH-200 ↗

Common skills at DevOps / CI-CD · Associate

Shared competencies for the DevOps/CI-CD domain at Associate level, independent of vendor or platform.

• YAML configuration and syntax — Indentation-sensitive structured markup; used by Kubernetes, Docker Compose, Ansible, GitHub Actions, GitLab CI, and most modern CI/CD platforms. Whitespace errors are common; candidates must debug and author YAML by hand.
• Docker containerization — Image layering, Dockerfile authoring, registry push/pull, container networking, and runtime flags. GitHub Actions uses Docker heavily for actions; understanding image efficiency (layer caching) is important.
• Git fundamentals — Clone, branch, merge, rebase, cherry-pick, conflict resolution, and reflog. GitHub Actions is deeply integrated with Git; workflows are triggered by Git events (push, pull_request).
• Scripting (Bash, Python, shell) — Automation and testing; common in build steps and custom actions. Bash is the default in most GitHub Actions runners (Ubuntu).
• Networking basics — HTTP/HTTPS, ports, DNS, firewalls, IP allowlisting. Critical for runners behind corporate proxies and for deploying to cloud platforms.
• Cloud platform basics — EC2, App Service, Container Registry, and cloud credential management. Many workflows deploy to cloud; understanding platform-specific APIs is essential.

Recommended courses at DevOps / CI-CD · Associate

Course-selection rule: Each course must cover GH-200 exam objectives specifically, not "GitHub in general." The Udemy exam-question courses and MeasureUp practice exams are most directly aligned to the 2026 exam format.

Practice exams

Books

Book note: GitHub Actions is a rapidly evolving platform. The Manning (2023) and O'Reilly (2022) titles provide solid foundational coverage, but the exam changed significantly in January 2026. Pair any book study with the official Microsoft Learn study guide and the latest MeasureUp practice exams.

Exam preparation strategy

Recommended study timeline: 4–8 weeks for Associate-level readiness (assumes intermediate GitHub + CI/CD familiarity).

Phase 1: Official Study Guide (1–2 weeks)

• Read Microsoft Learn study guide end-to-end: learn.microsoft.com/credentials/certifications/resources/study-guides/gh-200
• Take notes on exam objectives and weighted domains (Author/Manage Workflows 20–25%, Manage Enterprise 15–20%, Consume Actions 20–25%, etc.)
• Review GitHub Actions documentation: docs.github.com/actions
• Understand the January 2026 exam changes: OIDC, enterprise runners, and security practices

Phase 2: Hands-on Laboratory (2–3 weeks)

• Set up a test repository on GitHub
• Author workflows covering all exam domains: push triggers, pull_request event filtering, matrix builds, conditional execution, reusable workflows
• Create and publish a custom JavaScript or Docker container action
• Integrate workflows with a third-party service (Slack, AWS, Docker Hub, npm registry)
• Test OIDC-based passwordless cloud deployments (AWS STS, Azure Workload Identity) if available
• Debug workflow runs using GitHub UI logs and action diagnostics
• Test runner management (if you have GitHub Enterprise or a self-hosted runner environment)

Phase 3: Practice Exams (1–2 weeks)

• Complete MeasureUp full-length practice test (most closely aligned to real exam format and difficulty)
• Review all incorrect answers; note knowledge gaps and bookmark Microsoft Learn sections
• Complete Udemy GH-200 practice exams (500+ questions across multiple full exams)
• Use CertificationPractice.com free tests (390 questions) for additional drilling and weak-area reinforcement

Phase 4: Final Review (3–5 days)

• Review exam objectives one final time; map each objective to a concrete scenario
• Flashcards on YAML syntax edge cases (indentation-sensitive, special characters, flow vs. block style)
• Workflow context variables automatic recall: github, runner, env, secrets, vars, inputs, matrix, needs, strategy
• OIDC token exchange flow and cloud credential management — common tricky scenario
• Schedule exam on Pearson VUE; confirm test center or online proctoring setup and identification requirements

Typical job titles at DevOps / CI-CD · Associate

DevOps Engineer · CI/CD Engineer · Release Engineer · Site Reliability Engineer (SRE) · Software Engineer (Build/Infrastructure focus) · Platform Engineer · Infrastructure Automation Engineer · GitHub Developer

Context: These roles design and maintain CI/CD pipelines, automate deployments, manage production infrastructure, and ensure system reliability at scale. GitHub Actions experience is increasingly listed as "required" or "preferred" on job boards for mid-market and enterprise teams using GitHub Enterprise. Remote-friendly; common across SaaS, fintech, and enterprise software vendors.

(Job titles drawn from 2026 job boards (LinkedIn, Glassdoor, Indeed) listing GitHub Actions experience as required or preferred. Not all positions require this specific cert, but it validates hands-on workflow design and automation expertise valued in these roles.)

Salary

Salary note: GitHub Actions certification-specific salary uplift data is not yet widely available; these ranges reflect DevOps and CI/CD engineer roles that commonly require or prefer GitHub Actions expertise. Certification value is highest when combined with 2+ years of hands-on GitHub/CI-CD experience.

Skills validated

Technologies and practices specifically tested by the GH-200 exam.

Workflow Authoring & Configuration

• YAML syntax and workflow file structure (triggers, jobs, steps, run / uses directives)
• Event filtering and workflow triggers (push, pull_request, schedule, workflow_dispatch, webhook events)
• Reusable workflows (calling workflows from workflows across repositories)
• Workflow visualization, logging, and debugging (GitHub UI, workflow run history, action logs)

Contexts, Metadata & Runtime Variables

• Workflow contexts (github, runner, env, secrets, vars, inputs, matrix, needs, strategy, job, steps)
• Environment variables and variable interpolation in YAML
• Encrypted secrets at repository, environment, and organization scopes
• Matrix strategy for parallel test execution across platforms/versions

Actions (Built-in, Pre-built, Custom)

• Pre-built actions from GitHub Marketplace (checkout, upload-artifact, download-artifact, deploy-to-production)
• Docker container actions (docker://, -uses- directives)
• Composite actions (bundled shell / JavaScript steps)
• JavaScript/TypeScript action development and metadata (action.yml)

Security & Deployment

• OpenID Connect (OIDC) federation for passwordless cloud deployments (AWS, Azure, GCP)
• Encrypted secrets management and preventing secrets leakage in logs
• Branch protection rules and status checks
• Deployment environments and approval gates

Self-Hosted Runners & Enterprise

• Runner installation, configuration, and updates (Ubuntu, macOS, Windows, Docker)
• Self-hosted runner groups and assignment policies
• Resource management and scaling (runner pools, concurrency limits)
• Organization-level runner management and compliance
• GitHub Enterprise Server (GHES) runner configuration and administration

Integration & Automation

• Third-party service integrations (AWS, Azure, Docker Hub, npm, Slack, etc.)
• GitHub Packages (npm, Maven, NuGet, Docker) integration in workflows
• Artifact upload/download for inter-step communication
• Workflow status and failure handling (if conditions, continue-on-error)

Related certifications

• Stacks with: GitHub Foundations (GH-900) ↗ (file not yet created) — entry-level GitHub fundamentals; lower weight than Actions
• Stacks with: GitHub Administration (GH-100) ↗ (file not yet created) — enterprise GitHub management; orthogonal focus
• Complements: AWS Certified DevOps Engineer – Professional ↗ (file not yet created) — AWS-specific orchestration; GitHub Actions common in hybrid stacks
• Complements: Certified Kubernetes Administrator (CKA) ↗ (file not yet created) — container orchestration; GitHub Actions often deploys to Kubernetes
• Prerequisite for: GitHub Copilot (GH-300) ↗ (file not yet created) — AI-assisted workflow authoring; builds on Actions knowledge
• Equivalents at this level: GitLab Certified Associate ↗ (file not yet created) — GitLab CI/CD equivalent
• Vendor overview: GitHub Overview ↗ (file not yet created)

Sources

• GitHub Actions Certification (Microsoft Learn)
• Study Guide for Exam GH-200
• About GitHub Certifications (GitHub Docs)
• Registering for GitHub Certifications Exam
• GitHub Learn: GitHub Actions Certification
• MeasureUp GitHub Actions Practice Test
• GitHub Actions Deep Dive (A Cloud Guru)
• Udemy: The Complete GitHub Actions & Workflows Guide
• KodeKloud GitHub Actions Certification Course
• Tutorials Dojo GH-200 Study Path
• Robert Half 2026 Technology Salary Guide
• Glassdoor DevOps Engineer Salaries
• PayScale South Africa DevOps Engineer
• Manning: GitHub Actions in Action
• O'Reilly: Learning GitHub Actions

Last verified: 2026-05-01

Parent ecosystem: GitHub Ecosystem — not yet created

Parent domain: DevOps / CI-CD — not yet created

Vendor overview: GitHub Vendor Overview — not yet created