Git & GitHub Mastery Quiz — Quiz

Undoing changes, rebasing, tags, pull requests, CI, stash, cherry-pick and bisect. · 10 questions

Question 1 of 10

Which command unstages a file but keeps your edits?

agit restore --staged file.pybgit reset --hardcgit revert file.pydgit rm file.py

Question 2 of 10

A commit already pushed to `main` introduced a bug. What is the safest way to undo it?

agit reset --hard HEAD~1 and force-pushbgit revert <sha>cDelete the repositorydgit commit --amend

Question 3 of 10

Why doesn't adding `db.sqlite3` to `.gitignore` stop Git from tracking it?

a.gitignore only works on WindowsbPatterns need a leading slashcThe file is already tracked; .gitignore only affects untracked filesdSQLite files cannot be ignored

Question 4 of 10

Where do GitHub Actions workflow files live?

aIn the repo root as actions.ymlbIn GitHub account settings onlycIn a .git/hooks folderdIn the .github/workflows/ directory

Question 5 of 10

What does this sequence do?

git reset --soft HEAD~3
git commit -m "Add GST report"

aDeletes the last three commits and their changesbReverts three commits on the remotecSquashes the last three commits into one, keeping all changesdCreates three new branches

Question 6 of 10

Why is `git push --force-with-lease` preferred over `git push --force` after a rebase?

aIt refuses to overwrite commits someone else pushed since your last fetchbIt is fastercIt also pushes tagsdIt avoids the need to rebase

Question 7 of 10

You need one bug-fix commit from `develop` on `release/2.3` without merging everything else. Use…

agit stashbgit bisectcgit rebase developdgit cherry-pick <sha>

Question 8 of 10

Which statement about tags is correct?

agit push sends all tags by defaultbAnnotated tags store author, date and a message; tags must be pushed explicitlycTags move forward with each new commitdTags can only point to the latest commit

Question 9 of 10

Roughly how many test steps does `git bisect` need to find a bad commit among about 1,000 commits?

aAbout 10bAbout 100cAbout 500dAbout 1,000

Question 10 of 10

What does `git bisect run` use to decide whether each commit is good or bad?

git bisect start HEAD v2.1.0
git bisect run python manage.py test billing

aThe commit messagebWhether the files changedcThe exit code of the command: 0 is good, non-zero is baddThe author of the commit