Backticks in a double-quoted git -m message get command-substituted by bash

Running git commit -m "..." with a double-quoted message that contains backtick-wrapped code identifiers (e.g. a function name) makes bash perform command substitution on the backtick spans BEFORE git sees the message. Backticks pair up sequentially across the whole string, so odd spans run as shell commands (you may see cmd: command not found on stderr) and get replaced by their empty output — silently deleting words from the commit message. Fix: write the message to a file and use git commit -F file (or single-quote the -m string, or escape the backticks). Verify with git log -1 --format=%B after committing messages that contain code.