# Git Commit Message

## git commit message template 적용하기

## .gitmessage 파일 생성하기

```shell
touch .gitmessage
```

## .gitconfig 파일 수정하여 템플릿 적용하기

### Global 적용

```shell
git config --global commit.template [template 파일]
git config --global commit.template .gitmessage
```

### Repository 별 적용

```shell
git config commit.template [template 파일]
git config commit.template .gitmessage
```

## .gitmessage template 예시

```shell
# <branch-name>: <subject>
# - content
# - content

######## Maximum length of content is 72 ########### -> |
# issue track number (#number)
# --- COMMIT END ---
# <type> Title
#   feature : New feature
#   fix     : Fix bug
#   refactor: Refactor code
#   style   : Change style of code(white space, semicolon etc)
#   test    : Add/Change/Delete test case
#   docs    : Add/Change/Delete document
#   build   : Change in build script
#   ci      : Change in ci script
#   chore   : etc
# ------------------
#     Capitalize the subject line
#     Use imperitive mood in subject
#     Do not use period at the end of subject
#     Seperate subject and content with a blank line
#     Use the body explain "what" and "why" vs "how"
#     Use "-" when content contains multiline
# ------------------
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://pm1100tm.gitbook.io/devnote/git/git-commit-message.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.