Final assessment

Twelve questions across the whole course. Score 70% or more to pass and unlock your certificate. You can retake it as often as you like.

Finish every lesson to earn the certificate — you can take the assessment any time.

Which description of a Git branch is accurate?

A full copy of the project’s files stored in its own folder.
A named, movable pointer to one commit; the history comes from following parents.
A folder inside .git holding every commit made on that branch.
The copy of the repository that lives on GitHub.

You made two commits on main that were meant for a new branch. Nothing is pushed yet. What’s the cleanest fix?

git revert HEAD~2..HEAD, then redo the work on a branch.
git switch -c contact-form and carry on.
git push, then fix it on GitHub.
git branch contact-form, git reset --hard origin/main, then git switch contact-form.

Which command lists the commits on feature that are not on main?

With pull.rebase set to true, git pull stops with a conflict in index.html. You’ve fixed the file. What finishes the job?

You force-deleted experiment with git branch -D and then remembered it had a commit you need. How do you get it back?

Your team agrees that nobody pushes to main directly and every pull request must pass CI. What enforces that?

A branch ruleset on main with Require a pull request and Require status checks to pass.
A note in CONTRIBUTING.md.
A workflow that reverts any direct push to main.
Adding main to .gitignore.

Which of these is safe to do on a branch your teammates have already pulled?

styles.css has two unrelated changes: a colour fix and the start of a new layout. You want to commit only the colour fix. What do you use?

Which statement about SSH authentication with GitHub is true?

You paste your private key into GitHub so it can verify you.
SSH keys expire every 30 days and must be regenerated.
Once SSH is set up, every remote uses it automatically.
You add the .pub public key to GitHub, and the private key stays on your machine.

main hasn’t moved since you created footer, but you want main’s history to show the footer work as one grouped feature. Which command?

In a fork workflow, where does your feature branch go before you open the pull request?

Directly to the original repository (upstream).
Nowhere; GitHub reads branches from your laptop.
To your fork (origin), then the pull request goes from your fork’s branch to the original’s main.
To your fork’s main branch.

A workflow at .github/workflow/ci.yml never runs on pull requests, and the Actions tab shows nothing. What’s the most likely cause?

12 questions unanswered