| 일 | 월 | 화 | 수 | 목 | 금 | 토 |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |
Tags
- 캐나다이민 #캘거리 #PGWP #유학후이민
- 1bed
- 개발자
- jiffy #in a jiffy #soon
- Data Annotation #데이터 라벨링 #크라우드웍스 #crowdworks #AI
- 오락실게임 #추억의 게임 #월강보합 #Pnadora #레트로시티
- C#
- html5
- 아케이드 #Arcade #
- 토론토부동산
- HTML5 #생산성
- 캐나다이민 #캘거리 #알버타 #BVC
- Modern javascript #ES6
- Bragg Creek #캘거리에서 갈만한곳 #피크닉장소 #알버타 #Forget me not
- 캐나다 동부 #온타리오 #주이동 #이직 #IT취업 #해외취업 #온타리오
- ping #ping us #ping 의미
- 주식투자 #캐나다 #캐나다주식 # ETF #BMO #Vanguard #iShares #증권계좌
- iphone 재활용
- SVN #CVS #Sourse Safe #형상관리
- 아파치 #node.js 연동 #리눅스
- 인명사전
- 2020년 결산 #주식 #삼성전기 #삼성전자 #다나와
- 캐나다이민 #유학후이민 #캘거리 #입국심사 #캐나다
- Brendan Eich
- ESL #유스호스텔 #캘거리 #Calgary Library Service #캐나다
- PGWP #캐나다이민 #캘거리
- 캐나다부동산
- 개발자어록
- HTML #Meta tag
- Anders Hejsberg
Archives
- Today
- Total
캐나다 전산실 근무자
Writing Meaningful Git Commit Messages 본문
Commit Message Format
Each commit message consists of a header, a body and an optional footer. The header has a special format that includes a type, a scope, and a subject:
<type>(<scope>): <subject> <BLANK LINE> <body>><BLANK LINE> <footer> Types of commit messages:
- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
- ci: Changes to CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
- docs: Documentation only changes
- feat: A new feature
- fix: A bug fix
- perf: A code change that improves performance
- refactor: A code change that neither fixes a bug nor adds a feature
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- test: Adding missing tests or correcting existing tests
Scope
The candidates for scope depends on the project and the technologies being used. It is fairly up to the developer to select a scope. (Angular uses its specific set of scopes.)
Subject
The subject contains a succinct description of the change:
- use the imperative, present tense: “change” not “changed” nor “changes”
- don’t capitalize the first letter
- no dot/period (.) at the end
Footer (Optional)
Footer is used for citing issues that this commit closes (if any).
Examples
docs(server): add javadoc comments on methods This message implies that the changes made in this commit are only concerned with documentation changes (or the like) in server side code.
feat(core): add new command 'Upload' to UI Adding a new feature — to the core functionality of the application.
fix: update GET headers (#142) Fix errors pertaining to HTTP GET headers which close the issue 142.
'개발관련-이것저것' 카테고리의 다른 글
| [리눅스 환경] How to install Node.js on a VPS or a Dedicated server (e.g. 김치하우스 캘거리) (0) | 2020.10.26 |
|---|---|
| Github opensource 참여하기 (0) | 2020.07.30 |
| Web API (0) | 2019.01.08 |
| SourceTree 에서 특정 파일 커밋 제외시키기 (0) | 2018.06.20 |
| Debug Classic ASP in Visual Studio (0) | 2014.12.25 |
'개발관련-이것저것' Related Articles
more
Comments