GIT 커밋 컨벤션

Commit Message Structure

기본적으로 커밋 메세지는 아래와 같이 제목/본문/꼬리말로 구성한다

type : subject

body

feat: Summarize changes in around 50 characters or less [#123, #456, #789]

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of the commit and the rest of the text as the body. The
blank line separating the summary from the body is critical (unless
you omit the body entirely); various tools like `log`, `shortlog`
and `rebase` can get confused if you run the two together.

Explain the problem that this commit is solving. Focus on why you
are making this change as opposed to how (the code explains that).
Are there side effects or other unintuitive consequenses of this
change? Here's the place to explain them.

Further paragraphs come after blank lines.

 - Bullet points are okay, too

 - Typically a hyphen or asterisk is used for the bullet, preceded
   by a single space, with blank lines in between, but conventions
   vary here

If you use an issue tracker, put references to them at the bottom,
like this:

• type
  • 과거시제 사용하지 않고 명령어로 작성
    • fix, add …
• subject
  • 50자 이하
• body (선택사항)
  • 부연설명이 필요하거나 커밋의 이유를 설명할 경우 작성
  • 72자를 넘기지 않고 제목과 구분되기 위해 한칸 띄어 작성

PR / MR 가이드

• Merge 형식

  • 제목

    • 기능: 작업내역[JIRA 티켓]
    • ex) refactor: auth 페이지 사용하지 않는 변수 제거 [COMMWEBFNT-217]

  • 내용

    ### Description
    
    설명
    
    ### Changes
    
    변경사항
    
    ### Test Checklist
    
    테스트 항목
    

• master, develop branch에는 commit할 수 없습니다.

• master는 prod에 배포하는 branch이기 때문에 주의해주세요.

branch