개발용 브랜치로 be 브랜치 대신 develop 브랜치 사용 #607
Merged
Conversation
This file contains 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
[BE/FIX] 켈린더 상세 오늘 먹은 음식 조회 안 되는 오류 해결
인증 코드가 회색 배경 안에 보이도록 css를 추가하였습니다.
[BE/FEAT] 이메일 인증 방식 변경
[BE/FEAT] Swagger 관련 요청 로깅에서 제외
약관 미동의 시 예외 발생
[BE/FEAT] 약관 및 개인 정보 처리 방침 수정하기
[BE/FEAT] 앱 버전 조회하기
[BE/FIX] 로컬 및 개발 환경 docker - environment 수정
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
기존에 하나의 레포에서 AOS, BE, AI 가 동시에 개발하여 be 브랜치를 사용하였는데 분야별로 다른 레포로 이동하여 레포를 develop으로 이동하고자 합니다.