More study resources

About this exam

The GitHub Foundations credential is the entry point in GitHub's certification lineup, reached from the Certifications link under the Developers / Learn section of github.com. It is aimed at people who already work with repositories - developers, students, DevOps and project staff - and who want external validation that they understand how GitHub's platform fits together: repository hosting, code review and collaboration as the core, with Actions for CI/CD automation, Code Quality, Code Security and Secret Protection, Codespaces cloud development environments, and Copilot for AI-assisted work forming the surrounding surface. Preparation is self-directed using GitHub's own materials: GitHub Skills interactive exercises that run inside your own copy of a real project, the documentation quickstart guides, the Resource center's ebooks, events and webinars, the GitHub Blog and Changelog, and GitHub's YouTube channel and podcast. One caution matters before you book anything: the GitHub pages retrieved for this guide describe products and learning resources, not exam logistics. Question count, time limit, passing score, fee, retake rules and validity period are not published there, so treat any figure you see elsewhere as unverified until you confirm it on GitHub's official certification page.

What you'll study

Common questions

About GitHub Foundations preparation

What should I actually study for a GitHub Foundations exam?

Start from GitHub's own product taxonomy rather than a command cheat sheet. The platform areas GitHub documents are repository hosting, code review and collaboration, Actions, Code Quality, Code Security, Secret Protection, Codespaces and Copilot. Be able to explain what each one does and where it sits in a project's lifecycle.

How many questions are on the exam, and how long do I get?

Those logistics are not stated in the GitHub pages retrieved for this guide, which cover products and learning resources only. Do not rely on question counts or time limits quoted by third-party prep sites. Check GitHub's official certification page before you schedule so you plan around confirmed numbers.

How hard is it, and how much experience do I need?

No difficulty rating is published in the retrieved sources. The credential is a foundations-level one, so it rewards candidates who have genuinely used repositories, branches, pull requests and reviews rather than candidates who have only read about them. Hands-on comfort with a real project is the most reliable predictor of readiness.

How should I order my studying?

Work from doing to reading. Begin with GitHub Skills interactive exercises, which run inside your own copy of a real project, then move to the documentation quickstart guides for the areas you were weakest on, then use the Resource center webinars and ebooks for breadth. Finish by skimming the Changelog so your product knowledge is current.

Why do candidates fail this kind of exam?

The usual causes are memorising commands instead of workflows, skipping collaboration concepts such as pull requests and review, and studying from material that predates recent platform changes. GitHub ships features continuously; an answer that felt right a year ago may describe a renamed or restructured product area.

Can I retake the exam if I fail, and does it expire?

Neither retake rules nor certificate validity is stated in the GitHub pages retrieved here. Those are administration terms, not product terms, and they change. Confirm both - and any waiting period between attempts - on GitHub's official certification page before you pay for a sitting.

What does the certification cost?

The fee is not published in the retrieved sources, so this guide does not quote one. Pricing for GitHub certifications is set on GitHub's official certification page and may vary by region or partner. Check there rather than budgeting from an outdated figure quoted in a forum or blog post.

Are GitHub's own learning resources enough, or do I need a course?

GitHub provides substantial free material: GitHub Skills exercises, documentation quickstart guides, Resource center ebooks, events and webinars, the Blog, and the YouTube channel and podcast. Whether that is sufficient depends on how much hands-on repository work you have already done. Use a paid course only to fill specific gaps.