.gitmessage

# <type>(<scope>) #NNN: <subject>   (<= 72 chars, imperative; e.g.
#   "fix(core) confluentinc#909: replace stale work container on rebalance")
#
# Body: what changed and why (wrap ~72).
#
# ISSUE REFS GO AT THE FRONT; THE END BELONGS TO THE PR NUMBER. On squash-merge
# GitHub appends `(#123)` to the subject, so a subject already ending in `(#41)`
# merges as `(#41) (#123)` -- two bare numbers, nothing to tell them apart.
#   this fork       -> `docs(mutation) astubbs#41: subject`
#   upstream        -> `fix(core) confluentinc#909: subject`
# Prefer this fork's mirror number when one exists: a bare `#909` autolinks to
# fork issue 909, which is not the upstream one you meant. Upstream provenance
# also belongs in the trailers below, which is where a tool can read it.
# See AGENTS.md "Commits" -- on a squash-merge the merged subject is the
# PR title, so the same rule governs both.
#
# --- Upstream trailers -------------------------------------------------------
# For commits that relate to upstream confluentinc/parallel-consumer, UNCOMMENT
# and fill in what applies (delete the rest). Comment/blank lines are stripped
# by git, so an untouched template adds nothing. Not needed for fork-only work
# (rebrand, release, dependabot, formatting). Field names follow Debian DEP-3.
# The machine-readable cache is src/docs/development/upstream-map.yaml -- update
# the matching entry there too.
#
# Upstream-Issue: confluentinc/parallel-consumer#NNN
# Upstream-PR: confluentinc/parallel-consumer#NNN
# Forwarded: <upstream comment URL | no | not-needed>
# Applied-Upstream: <no | commit:SHA | VERSION>