19 lines
1.2 KiB
Markdown
19 lines
1.2 KiB
Markdown
질문에 대한 답변과 설명은 한국어로 한다.
|
|
|
|
## Quality Assurance Guidelines
|
|
|
|
### Commit Standards
|
|
1. Write in Korean.
|
|
2. Use the present tense in the subject line (e.g., "Add feature" not "Added feature").
|
|
3. Keep the subject line to 50 characters or less.
|
|
4. Add a blank line between the subject and body.
|
|
5. Keep the body to 72 characters or less per line.
|
|
6. Within a paragraph, only break lines when the text exceeds 72 characters.
|
|
7. Describe changes to public API features and do not include implementation details such as package-private code.
|
|
8. Do not mention test code in commit messages.
|
|
9. Do not use any prefix (such as "fix:", "update:", "docs:", "feat:", etc.) in the subject line.
|
|
10. Do not start the subject line with a lowercase letter unless the first word is a function name or another identifier that is conventionally lowercase and there is a clear, justifiable reason for the exception. Otherwise, always start with an uppercase letter.
|
|
11. Do not include tool advertisements, branding, or promotional content in commit messages.
|
|
12. Use separate git commands to stage files before committing.
|
|
13. Always validate commits using `work/scripts/check-commit-message-rules.sh` and fix until validation passes.
|