The Developer Guide’s Workflow document includes appendices on how best to use Git: including advice on how best to organize commits and how to structure commit messages.
At the moment, we simply have a statement that "we follow" some particular set of guidelines. My concern is simply that we don't, or at least we're not required to. Softening the language to "we suggest", or similar, instead would resolve the issue as far as I'm concerned.
This ticket will
1. Determine what parts of those appendices may be requirements, if any.
2. Change the language to intentionally differentiate between suggestions and requirements (“we follow” or “we require")