docs: refine branch naming conventions#342
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
브랜치명 컨벤션에서
codex타입을 제거하고, 작업 성격 기반 타입을 우선 사용하도록 정리했습니다.Problem
브랜치 타입 목록에
codex가 포함되어 있어 작업 성격이 명확한 리팩터링/문서/수정 작업에도codex브랜치를 기본처럼 사용할 여지가 있었습니다.Solution
허용 브랜치 타입을
feat,fix,refactor,docs,hotfix중심으로 정리하고, 작업 성격이 명확하면 해당 타입을 우선 사용한다는 원칙을 추가했습니다.Changes
codex브랜치 타입 설명 삭제codex/readme-update예시 삭제Example
문서 변경이라 별도 사용 예시 없음
Related Issues
없음