Skip to content

Instantly share code, notes, and snippets.

@kense-lab

kense-lab/.git-commit-template.txt

Forked from jmaxhu/.git-commit-template.txt
Created March 20, 2021 04:11
Show Gist options
  • Save kense-lab/5be9a550bd4e9ff7c6098f1bc3b20066 to your computer and use it in GitHub Desktop.
Save kense-lab/5be9a550bd4e9ff7c6098f1bc3b20066 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. @jmaxhu jmaxhu revised this gist Mar 11, 2016. 1 changed file with 24 additions and 26 deletions.
    50 changes: 24 additions & 26 deletions .git-commit-template.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -1,32 +1,30 @@
    # <type>: (If applied, this commit will...) <subject> (Max 50 char)
    # |<---- Using a Maximum Of 50 Characters ---->|
    # <类型>: (类型的值见下面描述) <主题> (最多50个字)

    # 解释为什么要做这些改动
    # |<---- 请限制每行最多72个字 ---->|

    # Explain why this change is being made
    # |<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->|
    # 提供相关文章和其它资源的链接和关键字
    # 例如: Github issue #23

    # Provide links or keys to any relevant tickets, articles or other resources
    # Example: Github issue #23

    # --- COMMIT END ---
    # Type can be
    # feat (new feature)
    # fix (bug fix)
    # docs (changes to documentation)
    # style (formatting, missing semi colons, etc; no code change)
    # refactor (refactoring production code)
    # test (adding missing tests, refactoring tests; no production code change)
    # chore (updating grunt tasks etc; no production code change)
    # --- 提交 结束 ---
    # 类型值包含
    # feat (新特性)
    # fix (bug修复)
    # docs (文档改动)
    # style (格式化, 缺失分号等; 不包括生产代码变动)
    # refactor (重构代码)
    # test (添加缺失的测试, 重构测试, 不包括生产代码变动)
    # chore (更新grunt任务等; 不包括生产代码变动)
    # --------------------
    # Remember to
    # Separate subject from body with a blank line
    # Limit the subject line to 50 characters
    # Capitalize the subject line
    # Do not end the subject line with a period
    # Use the imperative mood in the subject line
    # Wrap the body at 72 characters
    # Use the body to explain what and why vs. how
    # Can use multiple lines with "-" for bullet points in body
    # 注意
    # 主题和内容以一个空行分隔
    # 主题限制为最大50个字
    # 主题行大写
    # 主题行结束不用标点
    # 主题行使用祈使名
    # 内容每行72个字
    # 内容用于解释为什么和是什么,而不是怎么做
    # 内容多行时以'-'分隔
    # --------------------
    # For more information about this template, check out
    # 模板更多信息详见下面地址
    # https://gist.github.com/adeekshith/cd4c95a064977cdc6c50
  2. @adeekshith adeekshith revised this gist Mar 4, 2016. 1 changed file with 4 additions and 2 deletions.
    6 changes: 4 additions & 2 deletions .git-commit-template.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -1,7 +1,9 @@
    # <type>: (If applied, this commit will...) <subject> (Max 50 char)
    # |<---- Using a Maximum Of 50 Characters ---->|


    # Explain why this change is being made
    # |<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->|

    # Provide links or keys to any relevant tickets, articles or other resources
    # Example: Github issue #23
    @@ -26,5 +28,5 @@
    # Use the body to explain what and why vs. how
    # Can use multiple lines with "-" for bullet points in body
    # --------------------
    # For a full example of how to write a good commit message, check out
    # https://github.com/sparkbox/how_to/tree/master/style/git
    # For more information about this template, check out
    # https://gist.github.com/adeekshith/cd4c95a064977cdc6c50
  3. @adeekshith adeekshith revised this gist Mar 2, 2016. No changes.
  4. @adeekshith adeekshith revised this gist Mar 2, 2016. No changes.
  5. @adeekshith adeekshith revised this gist Feb 29, 2016. 1 changed file with 25 additions and 22 deletions.
    47 changes: 25 additions & 22 deletions .git-commit-template.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -1,27 +1,30 @@
    # Type(<scope>): <subject>
    # <type>: (If applied, this commit will...) <subject> (Max 50 char)

    # <body>

    # <footer>
    # Explain why this change is being made

    # Type should be one of the following:
    # * feat (new feature)
    # * fix (bug fix)
    # * docs (changes to documentation)
    # * style (formatting, missing semi colons, etc; no code change)
    # * refactor (refactoring production code)
    # * test (adding missing tests, refactoring tests; no production code change)
    # * chore (updating grunt tasks etc; no production code change)
    # Scope is just the scope of the change. Something like (admin) or (teacher).
    # Subject should use impertivite tone and say what you did.
    # The body should go into detail about changes made.
    # The footer should contain any JIRA (or other tool) issue references or actions.
    # Provide links or keys to any relevant tickets, articles or other resources
    # Example: Github issue #23

    # --- COMMIT END ---
    # Type can be
    # feat (new feature)
    # fix (bug fix)
    # docs (changes to documentation)
    # style (formatting, missing semi colons, etc; no code change)
    # refactor (refactoring production code)
    # test (adding missing tests, refactoring tests; no production code change)
    # chore (updating grunt tasks etc; no production code change)
    # --------------------
    # Remember to
    # Separate subject from body with a blank line
    # Limit the subject line to 50 characters
    # Capitalize the subject line
    # Do not end the subject line with a period
    # Use the imperative mood in the subject line
    # Wrap the body at 72 characters
    # Use the body to explain what and why vs. how
    # Can use multiple lines with "-" for bullet points in body
    # --------------------
    # For a full example of how to write a good commit message, check out
    # https://github.com/sparkbox/how_to/tree/master/style/git

    # ---------------------------------------------------------------------------------
    # Jira Issue Processing
    # ISSUE_KEY #comment This is a comment
    # ISSUE_KEY #done
    # ---------------------------------------------------------------------------------
    # https://github.com/sparkbox/how_to/tree/master/style/git
  6. @Linell Linell revised this gist Jun 2, 2015. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions .git-commit-template.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -1,5 +1,7 @@
    # Type(<scope>): <subject>

    # <body>

    # <footer>

    # Type should be one of the following:
  7. @Linell Linell created this gist Feb 12, 2015.
    25 changes: 25 additions & 0 deletions .git-commit-template.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,25 @@
    # Type(<scope>): <subject>
    # <body>
    # <footer>

    # Type should be one of the following:
    # * feat (new feature)
    # * fix (bug fix)
    # * docs (changes to documentation)
    # * style (formatting, missing semi colons, etc; no code change)
    # * refactor (refactoring production code)
    # * test (adding missing tests, refactoring tests; no production code change)
    # * chore (updating grunt tasks etc; no production code change)
    # Scope is just the scope of the change. Something like (admin) or (teacher).
    # Subject should use impertivite tone and say what you did.
    # The body should go into detail about changes made.
    # The footer should contain any JIRA (or other tool) issue references or actions.

    # For a full example of how to write a good commit message, check out
    # https://github.com/sparkbox/how_to/tree/master/style/git

    # ---------------------------------------------------------------------------------
    # Jira Issue Processing
    # ISSUE_KEY #comment This is a comment
    # ISSUE_KEY #done
    # ---------------------------------------------------------------------------------