"Gopher Robot - Possible problems detected"의 두 판 사이의 차이

(새 문서: ==개요== ;Gopher Robot (Gerrit) - Possible problems detected: * The commit title should start with the primary affected package name followed by a colon, like "net/http: improve [.....)
 
1번째 줄: 1번째 줄:
==개요==
==개요==
;Gopher Robot (Gerrit) - Possible problems detected:
;Gopher Robot (Gerrit) - Possible problems detected:
* The commit title should start with the primary affected package name followed by a colon, like "net/http: improve [...]".
* The commit title should start with the primary affected package name followed by a colon, like "net/http: improve [...]".
* The first word in the commit title after the package should be a lowercase English word (usually a verb).
* The first word in the commit title after the package should be a lowercase English word (usually a verb).
* Lines in the commit message should be wrapped at ~76 characters unless needed for things like URLs or tables. You have a 79 character line.
* Do you have the right bug reference format? For most repos outside the main go repo, the format is usually 'Fixes golang/go#12345' or 'Updates golang/go#12345' at the end of the commit message.


==참고==
==참고==

2024년 1월 12일 (금) 20:31 판

1 개요

Gopher Robot (Gerrit) - Possible problems detected
  • The commit title should start with the primary affected package name followed by a colon, like "net/http: improve [...]".
  • The first word in the commit title after the package should be a lowercase English word (usually a verb).
  • Lines in the commit message should be wrapped at ~76 characters unless needed for things like URLs or tables. You have a 79 character line.
  • Do you have the right bug reference format? For most repos outside the main go repo, the format is usually 'Fixes golang/go#12345' or 'Updates golang/go#12345' at the end of the commit message.

2 참고

문서 댓글 ({{ doc_comments.length }})
{{ comment.name }} {{ comment.created | snstime }}