(→개요) |
(→개요) |
||
| 4번째 줄: | 4번째 줄: | ||
* [[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 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 | * [[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 xx character line.]] | * [[Lines in the commit message should be wrapped at ~76 characters unless needed for things like URLs or tables. You have a xx 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.|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.]] | * [[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.|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월 23일 (화) 15:03 판
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 xx 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.
- 커밋 제목은 영향을 받는 주요 패키지 이름으로 시작하고 그 뒤에 콜론이 와야 합니다(예: "net/http: Improve [...]").
- 패키지 뒤 커밋 제목의 첫 번째 단어는 영어 소문자(보통 동사)여야 합니다.
- 커밋 메시지의 줄은 URL이나 테이블과 같은 항목에 필요한 경우를 제외하고 최대 76자로 줄바꿈되어야 합니다. xx개 문자가 있는 행이 있습니다.
- 올바른 버그 참조 형식이 있습니까? 기본 go 저장소 외부에 있는 대부분의 저장소의 경우, 형식은 일반적으로 커밋 메시지 끝에 'Fixes golang/go#12345' 또는 'Updates golang/go#12345'입니다.
2 같이 보기
3 참고
로그인하시면 댓글을 쓸 수 있습니다.
{{ comment.name }}
{{ comment.created | snstime }}
-
{{comment.page_title}} ―{{comment.name}}