chore: GitHub Actions 이미지 경로 동적화 및 프로젝트명/서비스명 uttae로 변경#133
Conversation
|
Warning Review limit reached
More reviews will be available in 49 minutes and 7 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthrough프로젝트 전반의 식별자, 샘플 DB 이름, Compose 프로젝트/네트워크 이름, CI 이미지 참조, 애플리케이션/문서 내 브랜드명이 how-about-us* 계열에서 uttae/utatae 계열로 일괄 변경되었습니다. 변경 사항프로젝트 이름 일괄 변경
예상 코드 검토 소요 시간🎯 3 (Moderate) | ⏱️ ~20 분 시
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 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 @.env.dev.example:
- Line 2: The integration test DB name is hardcoded in BaseIntegrationTest.java
via the PostgreSQLContainer.withDatabaseName("howaboutus_test"); update it to
match the .env.dev.example DB_NAME ("uttae") by changing the argument to "uttae"
or, better, read the DB name from the DB_NAME environment/property and pass that
value into PostgreSQLContainer.withDatabaseName(...) so the test container uses
the same DB name as the .env.dev.example.
In @.github/workflows/deploy-compose.yml:
- Line 30: DEPLOY_PATH value in the workflow should be updated or documented to
match the compose project name; change the DEPLOY_PATH variable in
.github/workflows/deploy-compose.yml from /opt/how-about-us-backend to a path
consistent with compose.app.prod.yaml's project name (name: uttae-api) or add a
clear inline comment stating this is a legacy path and why it differs,
referencing DEPLOY_PATH and the compose file's name: uttae-api so future readers
know the intended mapping.
In @.serena/memories/project_overview.md:
- Line 1: Condense the .serena/memories/project_overview.md into a brief "when
to read which document" index: remove inline detailed descriptions and escaped
newlines, replace the full stack/domain list with short pointers to AGENTS.md
and docs/ai/* (e.g., docs/ai/features.md, docs/ai/erd.md) for details, and add
status markers (미결 / 예상안 / 초안) next to any entry that is not final; keep only
high-level bullets like "Auth/Bookmarks/Places/Rooms — see docs/ai/features.md
(초안)" and "Architecture/Stack — see docs/ai/erd.md (미결)". Ensure uttae-backend
and AGENTS.md are referenced so readers know the source-of-truth, and remove any
duplicated technical lists from this file.
🪄 Autofix (Beta)
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: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 6a6cd807-a4fa-4767-b23e-f5e069c93c7a
📒 Files selected for processing (14)
.env.db.example.env.dev.example.github/workflows/deploy-compose.yml.serena/memories/project_overview.md.serena/project.ymlLICENSEREADME.mdbuild.gradlecompose.app.prod.yamlcompose.db.prod.yamlcompose.monitoring.prod.yamldocs/gstack/overview.mdsettings.gradlesrc/main/resources/application.yaml
… configure common uttae-network
…into feature/workflow-image-dynamic
There was a problem hiding this comment.
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 `@compose.app.dev.yaml`:
- Line 9: The docker compose env AI_BASE_URL set to "http://ai-server:8000" is
referenced by application.yaml's ai.base-url and used by TravelAiClientConfig
via RestClient.baseUrl(properties.baseUrl()); either add a service named
"ai-server" to your Compose (so the DNS resolves in the same network) or change
AI_BASE_URL to a reachable host/URL (e.g., the actual AI service container name,
hostname, or external address) so RestClient.baseUrl(properties.baseUrl())
points to a valid target at runtime.
🪄 Autofix (Beta)
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: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 7f52eb74-6cb0-48d3-9d81-83f9abc7c33d
📒 Files selected for processing (4)
README.mdcompose.app.dev.yamlcompose.db.dev.yamlcompose.db.prod.yaml
✅ Files skipped from review due to trivial changes (3)
- README.md
- compose.db.dev.yaml
- compose.db.prod.yaml
minbros
force-pushed
the
feature/workflow-image-dynamic
branch
from
ede605d to
1ad4888
Compare
…in dev compose files
|
minbros
temporarily deployed
to
production-monitoring
GitHub Actions
Inactive
minbros
temporarily deployed
to
production-monitoring
GitHub Actions
Inactive
minbros
temporarily deployed
to
production-monitoring
GitHub Actions
Inactive
1 participant
변경 내용
deploy-compose.yml)에서 하드코딩된backend-server이미지 경로를${{ github.repository }}를 사용하여 동적으로 가져오도록 수정compose.app.prod.yaml,compose.db.prod.yaml,compose.monitoring.prod.yaml)의 프로젝트명을uttae-*(예:uttae-api,uttae-data,uttae-monitoring)로 수정하고 Caddy 이미지명을uttae-caddy로 수정application.yaml내spring.application.name)을uttae-backend로 변경.env.db.example,.env.dev.example) 내 기본 데이터베이스 이름을uttae로 변경uttae-backend로 변경우리어때에서우때로 변경변경 이유
우리어때(how-about-us)에서우때(uttae)로 브랜드명이 전환됨에 따라, 설정 파일 및 문서 전반의 메타데이터와 명칭을 이에 일치시키고 이미지 경로를 동적화하여 하드코딩을 제거하기 위함테스트
./gradlew build(Checkstyle 검증 완료)/review-code-against-docs스킬로 검증체크리스트
하네스 변경 체크리스트
Summary by CodeRabbit