But a commit message in an arbitrary project is not where you give someone a lesson about nginx rules. "nginx .conf files must be in us-ascii" is maybe a good

But a commit message in an arbitrary project is not where you give someone a lesson about nginx rules. "nginx .conf files must be in us-ascii" is maybe a good bug or pull request title, but it may correspond to multiple commits that do different things, but it doesn't tell me what's happening. Is this converting a file to us-ascii, is this writing a tool to convert files to ASCII, is this updating documentation, is it creating a test, some combination? Leading with what, not why addresses that confusion.