Markdownμ ν μ€νΈ κΈ°λ°μ λ§ν¬μ μΈμ΄λ‘ 2004λ 쑴그루λ²μ μν΄ λ§λ€μ΄μ‘μΌλ©° μ½κ² μ°κ³ μ½μ μ μμΌλ©° HTMLλ‘ λ³νμ΄ κ°λ₯νλ€. νΉμκΈ°νΈμ λ¬Έμλ₯Ό μ΄μ©ν λ§€μ° κ°λ¨ν ꡬ쑰μ λ¬Έλ²μ μ¬μ©νμ¬ μΉμμλ λ³΄λ€ λΉ λ₯΄κ² 컨ν μΈ λ₯Ό μμ±νκ³ λ³΄λ€ μ§κ΄μ μΌλ‘ μΈμν μ μλ€. λ§ν¬λ€μ΄μ΄ μ΅κ·Ό κ°κ΄λ°κΈ° μμν μ΄μ λ κΉν(https://github.com) λλΆμ΄λ€. κΉνμ μ μ₯μRepositoryμ κ΄ν μ 보λ₯Ό κΈ°λ‘νλ README.mdλ κΉνμ μ¬μ©νλ μ¬λμ΄λΌλ©΄ λꡬλ κ°μ₯ λ¨Όμ μ νκ² λλ λ§ν¬λ€μ΄ λ¬Έμμλ€. λ§ν¬λ€μ΄μ ν΅ν΄μ μ€μΉλ°©λ², μμ€μ½λ μ€λͺ , μ΄μ λ±μ κ°λ¨νκ² κΈ°λ‘νκ³ κ°λ μ±μ λμΌ μ μλ€λ κ°μ μ΄ λΆκ°λλ©΄μ μ μ μ¬λ¬ κ³³μΌλ‘ νΌμ Έκ°κ² λλ€.
π€
In the last few years, the number of programmers concerned about writing structured commit messages have dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developers during debugging process.
This document borrows some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.