The First Bad Commit
check.sh exits with 0 while the settings are right and with 1 once they are broken. They were right at the tag good, and they are broken at the latest commit. Print the message of the first commit where the check fails, and nothing else. End where you started: on main, at its latest commit.
Example 1
starts as
* 8ddef3f (HEAD -> main) add the app * dfa0f68 more notes * 79c9d24 tune the rate * 52ff0f6 change the mode * 3f4e337 add notes * 9c67daf (tag: good) first commit nothing to commit check.sh: grep -q '^rate=0.2$' settings.txt
ends as
printed: tune the rate on branch: main at the commit: add the app
Constraints
- 3 to 9 commits after
good - Once the check fails, it fails in every later commit
Write it in your browser, against the clock. The model script, with a note on each command it uses, comes after.
More Git problems
- Three Into OneHard
- Undo the MergeHard
- When Was It AddedHard
- A New BranchBeginner
- Back to MainBeginner
- Commit the ChangeBeginner
- Commit the New FileBeginner
- How Many CommitsBeginner