Writing good commit messagesGood commit messages serve at least three important purposes: To speed up the reviewing process. To help us write a good release note. To help the future maintainers of Erlang/OTP (it could be you!), say five years into the future, to find out why a particular change was made to the code or why a specific feature was added. Structure your commit message like this: From: https://git-scm.com/book/ch
Amazon.co.jp: すごいErlangゆかいに学ぼう!: Fred Hebert (著), 山口能迪 (翻訳): 本
