Git Certificate
Earn the git certificate by passing the exam and demonstrating recovery + collaboration skills.
Certificate outline
EXAMPLE
# Git certificate - outline ## Part 1 - exam (45 min) Topics: - Working tree, index, HEAD - Branching strategies (trunk-based, GitFlow, environment branches) - Merge vs rebase vs cherry-pick - Recovery: reflog, bisect, restoring lost work - Collaboration: signed commits, CODEOWNERS, protected branches - Submodules vs subtree vs monorepo Passing mark: 70 percent. ## Part 2 - practical (take-home, ~3 hours) Demonstrate the skills end-to-end: Task A - Recovery: - Given a repo with a recent bad force-push, recover the lost branch using reflog - Document the recovery commands you used Task B - Clean history: - Take a messy 12-commit feature branch and rebase it into 3 logical commits - Use --autosquash with --fixup commits Task C - Bisect: - Find the commit that introduced a regression in a small repo - Document the bisect transcript Task D - Collaboration: - Fork a public repo, add CODEOWNERS, sign your commits, open a PR with a clean summary - Wire pre-commit hooks (prettier, eslint) so the PR is green Submit a Git repo + a markdown file documenting each step. ## Grading - Recovery (25 percent) - Clean history (25 percent) - Bisect transcript (20 percent) - Collaboration PR + signed commits (30 percent) ## Tips - The certificate is calibration; the documented transcripts are what employers will read - A clean rebase before a PR is the single best signal of seniority on a team
Why it matters
A git certificate worth showing is one where you can recover, refactor history, and collaborate without breaking a team. The documented transcripts are the actual signal - the exam is just a filter.
Tip: Tweak the snippet with Try it Yourself », then sit the quiz at the bottom of the page.
Discussion
Loading…