Skip to content

[CHORE] README 수정 - #229

Merged
ownue merged 5 commits into
developfrom
docs/new-readme
Aug 13, 2026
Merged

[CHORE] README 수정#229
ownue merged 5 commits into
developfrom
docs/new-readme

Conversation

@ownue

@ownue ownue commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

📍 개요

README 수정

⛓️‍💥 관련 이슈

X


🛠️ 작업 내용

  • 백엔드 리드미 수정 ㅎㅎ

🔥 리뷰 요청 사항

리뷰어가 중점적으로 확인해주었으면 하는 내용을 작성해주세요.

  • 잘못 들어간 내용이 없는지

📎 참고 사항

X

Summary by CodeRabbit

  • 문서
    • MuseReview Backend의 프로젝트 소개, 기술 스택, 아키텍처 및 인프라 정보를 추가했습니다.
    • 브랜치·커밋·PR·개발·로컬 환경 규칙을 표와 단계별 안내로 재구성했습니다.
    • AWS, Docker, Nginx, Redis 등 환경 정보를 보강했습니다.
    • 기본 빌드, 테스트 제외 빌드, 실행 명령과 Swagger 주소를 환경별로 정리했습니다.
    • 기존 PR 리뷰 태그 안내를 제거했습니다.

Updated README to reflect project name change and improved structure.
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@ownue, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 115 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 00b821b7-e5db-4dbc-b4b9-f49755629387

📥 Commits

Reviewing files that changed from the base of the PR and between 6573400 and 4760a5b.

📒 Files selected for processing (1)
  • README.md
📝 Walkthrough

Walkthrough

README.md를 MuseReview Backend 소개 문서로 개편했습니다. 프로젝트 아키텍처, 팀 정보, 개발 규칙, 환경 설정, 빌드 명령, Swagger UI 안내를 추가하거나 재구성했습니다.

Changes

프로젝트 소개와 팀 정보

Layer / File(s) Summary
프로젝트 소개와 팀 정보
README.md
MuseReview Backend의 기술 스택, 아키텍처, 인프라 구성, Backend Team 정보를 추가했습니다.

개발 규칙 정리

Layer / File(s) Summary
개발 규칙 정리
README.md
브랜치 전략, 브랜치 명명 규칙, 커밋 메시지 형식, PR 병합 조건, 개발 환경과 코드 스타일을 표와 예시로 정리했습니다. 기존 P1·P2·P3 리뷰 태그 안내는 삭제했습니다.

로컬 실행 안내

Layer / File(s) Summary
로컬 실행 안내
README.md
민감 정보 관리, 로컬 설정 절차, 운영체제별 빌드 명령, 테스트 제외 패키징 명령, Swagger UI 주소를 단계별 안내로 구성했습니다.

Estimated code review effort: 2 (Simple) | ~10 minutes

Mergeability Score: ⚪ Minimal · up to 65734

README.md has a minor heading hierarchy inconsistency that may affect document navigation or linting, but it has no product or runtime impact; the PR is merge-ready after routine documentation cleanup.

Poem

README에 새 지도가 펼쳐지고
브랜치 규칙이 줄을 맞추며
Swagger 주소가 길을 밝힌다
팀 정보도 한곳에 모여
문서 항해가 순항한다 🚢

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed README 전면 개편이라는 주요 변경 사항을 정확히 나타내며, 짧고 이해하기 쉽습니다.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/new-readme

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@rkdehdrbs7885-oss rkdehdrbs7885-oss left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

수고하셨습니다!

@on1yoneprivate on1yoneprivate left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

최고😍😍😍

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (1)
README.md (1)

17-19: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

배지 이미지에 대체 텍스트를 추가하세요.

markdownlint-cli2의 MD045 경고가 발생했습니다. 현재 8개의 기술 배지에 alt 속성이 없습니다. 이미지가 로드되지 않거나 스크린 리더를 사용할 때 기술 이름을 확인할 수 있도록 각 배지에 짧은 대체 텍스트를 추가하세요.

수정 예시
-<img src="https://img.shields.io/badge/Java%2017-007396?style=for-the-badge&logo=openjdk&logoColor=white"/>
-<img src="https://img.shields.io/badge/Spring%20Boot-6DB33F?style=for-the-badge&logo=springboot&logoColor=white"/>
-<img src="https://img.shields.io/badge/JPA-59666C?style=for-the-badge&logo=hibernate&logoColor=white"/>
+<img src="https://img.shields.io/badge/Java%2017-007396?style=for-the-badge&logo=openjdk&logoColor=white" alt="Java 17"/>
+<img src="https://img.shields.io/badge/Spring%20Boot-6DB33F?style=for-the-badge&logo=springboot&logoColor=white" alt="Spring Boot"/>
+<img src="https://img.shields.io/badge/JPA-59666C?style=for-the-badge&logo=hibernate&logoColor=white" alt="JPA"/>

Also applies to: 25-26, 32-34

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 17 - 19, README.md의 모든 기술 배지 이미지에 기술 이름을 나타내는 짧은 alt
텍스트를 추가하세요. 현재 배지와 추가 적용 대상인 모든 img 요소의 src 앞에 Markdown 이미지 대체 텍스트가 포함되도록 수정해
markdownlint MD045 경고를 제거하세요.

Source: Linters/SAST tools

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 269-281: Update the README Build section so the primary Windows
PowerShell and Git Bash/macOS commands use the standard build task without
excluding tests. Keep separate commands with -x test clearly labeled as optional
fast-packaging commands, and mention that they skip the test task.
- Around line 61-64: Update the README architecture description to explicitly
scope the Docker Compose and Nginx setup to the production environment, and
distinguish repository-managed deployment/configuration from external
infrastructure. Clarify that deployment uses EC2 and Docker Compose via cd.yml,
while PostgreSQL/RDS and S3 are external services configured by
application-prod.yml rather than managed in the repository.
- Around line 260-265: Update the local setup instructions in README.md by
replacing the build-only command for step 6 with separate Spring Boot bootRun
commands for PowerShell and Git Bash/macOS, using the Gradle wrapper
platform-specific syntax shown in the requested example.

---

Nitpick comments:
In `@README.md`:
- Around line 17-19: README.md의 모든 기술 배지 이미지에 기술 이름을 나타내는 짧은 alt 텍스트를 추가하세요. 현재
배지와 추가 적용 대상인 모든 img 요소의 src 앞에 Markdown 이미지 대체 텍스트가 포함되도록 수정해 markdownlint
MD045 경고를 제거하세요.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 0d94117a-954c-4130-88e8-66be97bdab52

📥 Commits

Reviewing files that changed from the base of the PR and between 92f647b and 597c6e0.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md Outdated
Comment thread README.md Outdated
Comment thread README.md Outdated

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 60-66: README.md의 “저장소에서 관리하는 구성”과 “저장소 외부에서 관리하는 인프라” 제목을 각각
####에서 ###로 변경해 Architecture 아래의 Markdown 제목 계층을 한 단계씩 일관되게 맞추세요.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 65d74fd6-196c-43c2-b5dd-7e3897d0e4bf

📥 Commits

Reviewing files that changed from the base of the PR and between 597c6e0 and 6573400.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md Outdated
ownue and others added 3 commits August 13, 2026 10:48
Removed unnecessary line breaks and updated architecture image.
…to docs/new-readme

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
@ownue
ownue merged commit b44ff9b into develop Aug 13, 2026
1 of 2 checks passed
@ownue
ownue deleted the docs/new-readme branch August 13, 2026 01:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants