dal4segno/Colosseum
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: 커밋 메시지 규칙에 chore 접두사 추가

Browse Source 
- AGENTS.md에 feat, fix와 함께 chore 접두사를 공식 커밋 타입으로 명시
- 씬/프리팹 정리, 에셋 재구성, 기타 유지보수성 작업에 chore를 사용하는 기준을 추가
- 큰 변경의 경우 한국어 bullet 본문을 함께 작성하는 커밋 메시지 규칙을 유지하도록 정리
This commit is contained in:
dal4segno
2026-03-24 16:54:37 +09:00
parent 829ff77e4b
commit 2d77bcea91
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
AGENTS.md
View File

@@ -330,7 +330,9 @@ public class NetworkedComponent : NetworkBehaviour
- After Unity-related edits, refresh or compile as needed and check the Unity console before proceeding. - After Unity-related edits, refresh or compile as needed and check the Unity console before proceeding.
- For networked play tests, prefer a temporary non-conflicting test port when needed and restore the default port after validation. - For networked play tests, prefer a temporary non-conflicting test port when needed and restore the default port after validation.
- The user has a strong project preference that play mode must be stopped before edits because network ports can remain occupied otherwise. - The user has a strong project preference that play mode must be stopped before edits because network ports can remain occupied otherwise.
- Commit messages should follow the recent project history style: use a type prefix such as `feat:` or `fix:` and describe the actual gameplay/UI/system change in Korean with enough detail to understand the scope from the log alone. - Commit messages should follow the recent project history style: use a type prefix such as `feat:`, `fix:`, or `chore:` and write the subject in Korean so the gameplay/UI/system change is clear from the log alone.
- When the change is substantial, include a blank line after the subject and add Korean bullet points that summarize the work by feature/purpose, similar to commit `0889bb0` (`feat: 드로그 집행 개시 패턴 및 낙인 디버프 추가`).
- Prefer the format `type: 한글 요약` for the subject, then `- 변경 사항` bullet lines for the body. Use `feat:` for feature work, `fix:` for bug fixes, and `chore:` for non-feature maintenance such as scene/prefab cleanup, asset reorganization, or other miscellaneous upkeep. The body should mention key implementation scope, affected systems/assets, and validation or rollback notes when relevant.
- All code comments and documentation should be in Korean - All code comments and documentation should be in Korean
- Use `[Min()]` attribute for numeric minimums in Inspector - Use `[Min()]` attribute for numeric minimums in Inspector
- Use `[TextArea]` for multi-line string fields - Use `[TextArea]` for multi-line string fields