GitHub Certifications

GitHub runs its own certification line, separate from the CNCF's, HashiCorp's, or AWS's — a handful of vendor-specific exams that check whether you actually know the platform your team is already standardized on, rather than Kubernetes or Terraform in the abstract. Of the four exams GitHub has published, two are directly relevant to a working DevOps engineer: GitHub Foundations, the entry-level baseline covering Git and the platform as a whole, and GitHub Actions, the one that maps straight onto the GitHub Actions tool page and CI/CD pipelines lesson elsewhere in this course. This page profiles both. Read the warning below before you plan around anything else on this page: GitHub has already restructured this program once, and the version most recently confirmed for this course routes exam delivery through Microsoft Learn's infrastructure with Pearson VUE proctoring — a real change from how these exams launched, and a strong signal that the lineup itself is worth re-checking, not just the price.

What GitHub Certifications are, and who they're for

☺ Like you're 10: Online, proctored, multiple-choice tests about GitHub itself — no live terminal, no cluster to fix, just questions about a platform you probably already use every day.

GitHub's certification program entered limited availability in 2022 and reached general availability in 2023, issuing digital badges through Credly the way most vendor certification programs do. Like the Terraform Associate and unlike the CKA, every GitHub certification is knowledge-based: multiple-choice and multiple-response questions delivered online with remote proctoring, no hands-on lab component, no live repository or workflow run graded on its end state. That makes preparation look like preparation for the Terraform Associate rather than the CKA — recognition and recall under a clock, not typed-out muscle memory.

The program targets people already working inside GitHub day to day rather than people evaluating whether to adopt it: engineers who open pull requests and read Actions logs as part of their normal job, administrators who manage organization and enterprise settings, and security engineers who triage code-scanning and secret-scanning alerts. None of the four exams formally requires a prerequisite, but GitHub's own preparation guidance has consistently assumed real, hands-on time on the platform first — these are not exams to attempt from documentation alone.

↗ GitHub official certifications page

The exam lineup — and why you must verify it yourself

☺ Like you're 10: There have been four exams. This program has already changed who runs it once, so treat "there are four" as a fact to double-check, not a fact to build a study plan on blindly.

As last confirmed for this course, GitHub's certification line names four exams. The two profiled in depth below are the ones that matter most to a DevOps engineer; the other two are named here for completeness because they sit closer to security and platform-administration roles.

• GitHub Foundations — the entry-level, platform-wide exam: Git fundamentals, the core GitHub workflow, collaboration features, and basic administration and security concepts. Profiled below.
• GitHub Actions — workflow authoring, the Actions ecosystem, and managing Actions at the organization or enterprise level. Profiled below, and the one that maps directly onto this course's GitHub Actions page.
• GitHub Advanced Security — code scanning, secret scanning, and dependency review (CodeQL and Dependabot). Closer to a DevSecOps engineer's exam than a DevOps engineer's; mentioned here for completeness rather than depth, and it overlaps with what this course covers at supply-chain security & SBOM and shift-left security for DevOps.
• GitHub Administration — managing organizations and enterprises: SSO/SAML, policy enforcement, billing, and migrations. Relevant to a platform or IT-admin role more than a delivery-focused DevOps role; not profiled in depth here.

GitHub Foundations: the entry-level baseline

☺ Like you're 10: Not CI/CD-specific at all — it's "do you actually know GitHub," the same way a driving test checks mirrors and indicators before anyone lets you near the motorway.

GitHub Foundations is the platform-wide exam GitHub itself has generally positioned as the natural starting point, though it is not a hard prerequisite for GitHub Actions. It checks breadth across the whole product rather than depth in any one corner of it, which makes it a fast, cheap way to formalize knowledge most engineers already have informally after a few months of daily GitHub use.

Topics it has generally covered, reconstructed here from the program's own stated scope and worth re-verifying against the current exam guide:

• Git and version control fundamentals — commits, branches, merges, and the difference between Git the tool and GitHub the platform built on top of it. Covered vendor-neutral in version control & branching.
• The core GitHub workflow — repositories, branch protection, pull requests, code review, issues, and Projects for lightweight planning.
• Collaboration and community features — Discussions, wikis, and the conventions around good commit messages and PR descriptions that make a repository legible to people who didn't write it.
• Introductory GitHub Copilot concepts — what Copilot is and where it fits in the day-to-day workflow, at an awareness level rather than deep configuration.
• Basic administration and security — two-factor authentication, the shape of GitHub's permission model at the repository and organization level, and where security settings live, without the depth of the dedicated Advanced Security or Administration exams.

Most DevOps engineers who've used GitHub daily for any real stretch of time will find Foundations closer to a confirmation than a learning exercise — its main value is credentialing knowledge you already hold, and giving a fast, no-prerequisite first badge to point to.

GitHub Actions: the exam that matters most to this course

☺ Like you're 10: This is the one that actually tests the pipeline skills — the workflow YAML, the marketplace, and the security habits, not just "have you used GitHub."

The GitHub Actions exam is the direct counterpart to this course's GitHub Actions page and the CI/CD pipelines lesson it sits under. Reconstructed here from GitHub's own published exam guidance, grouped into four areas — treat the grouping and any specific weighting you find elsewhere as directional, since GitHub has not consistently published fixed per-domain percentages the way the CNCF does for the CKA:

• Author and maintain workflows — the largest area in most published guidance. Workflow YAML anatomy (on:, jobs:, steps:), triggers and event filters, contexts and expressions (github., needs., secrets.), conditionals, matrix strategies, artifacts, caching, and the split between reusable workflows and composite actions.
• Consume workflows in GitHub Actions — runners (GitHub-hosted versus self-hosted), reading and troubleshooting workflow runs and logs, understanding what the auto-generated GITHUB_TOKEN can and can't do, and evaluating a marketplace action before trusting it in a pipeline.
• Author and maintain actions — building a custom action (JavaScript, Docker container, or composite), the action metadata file (action.yml), and publishing and versioning an action for others to consume.
• Manage GitHub Actions for the enterprise — organization- and enterprise-level policy: which actions are allowed to run at all, spending limits, self-hosted runner groups, and artifact and log retention settings.

The security instincts the exam rewards are the same ones the GitHub Actions tool page already teaches: pin marketplace actions to a full commit SHA rather than a mutable tag, scope the permissions: block down from its (formerly broad) default instead of leaving it implicit, and prefer short-lived OpenID Connect tokens over long-lived cloud credentials stored as repository secrets.

permissions:
  id-token: write        # required to request a short-lived OIDC token
  contents: read          # everything else defaults to none — name only what this job needs

jobs:
  deploy:
    runs-on: ubuntu-latest
    environment: production   # environment protection rules + required reviewers live here
    steps:
      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 — pinned to a commit SHA, not a mutable tag
      - uses: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502 # v4.0.2
        with:
          role-to-assume: arn:aws:iam::123456789012:role/gha-deploy
          aws-region: us-east-1
          # no long-lived aws-access-key-id / aws-secret-access-key anywhere in this file —
          # OIDC exchanges the id-token above for a short-lived credential at run time

Full syntax depth, the marketplace-pinning discussion, matrix builds, and the reusable-workflow-versus-composite-action distinction all live on the GitHub Actions tool page — this section names what the exam checks against that material, not a replacement for it.

How this maps onto the course

☺ Like you're 10: One tool page and one lesson do most of the heavy lifting; a couple of deep-dive pages cover the security-flavored corners.

Exam logistics — verify these yourself before you register

☺ Like you're 10: More than any other cert on this site, this is the one where "read the vendor's current page" isn't just good advice — the plumbing underneath it has already changed once.

Where it sits, and who should take it

☺ Like you're 10: Fast and cheap if your team already lives in GitHub. A weak substitute for a hands-on cert if the job actually needs you to prove you can operate infrastructure under a clock.

Set against the other certifications this course covers, GitHub's line is the most tool-specific and, historically, the least expensive to attempt — closer in shape to the Terraform Associate (knowledge-based, one vendor's product, no hands-on component) than to the CKA (performance-based, vendor-neutral platform).

Take GitHub Actions if: your organization has standardized on GitHub and GitHub Actions specifically, you want a fast, low-cost, knowledge-based credential to formalize what you already do daily, or you're the person other engineers already ask to review workflow files and want that informally recognized skill externally checked. Take GitHub Foundations first if: you're relatively new to the platform as a whole and want the broader baseline before narrowing into Actions — though note it is not a hard prerequisite. Consider skipping the whole line if: your actual gap is vendor-neutral CI/CD or infrastructure thinking rather than GitHub-specific product knowledge — the CI/CD pipelines and infrastructure as code lessons, or the Terraform Associate and CKA certifications, will transfer to more employers than a single-vendor credential will; or if your real interest is security rather than delivery, in which case GitHub Advanced Security — or this platform's DevSecOps course — is the better-targeted exam.