refactor: 스크립트 오타 수정

[Jjiggu]

작업 요약

띄어쓰기 오타 수정

Issue Link

#206

문제점 및 어려움

해결 방안

Reference

Summary by CodeRabbit

• Style

  • 코드 파일의 불필요한 공백 라인이 제거되었습니다.

• Chores

  • 배포 워크플로우의 파일 경로 지정 방식이 개선되었습니다. (기능에는 영향 없음)

[coderabbitai]

Warning

Rate limit exceeded

@Jjiggu has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 16 minutes and 16 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 0b1dd99 and ca12dee.

📒 Files selected for processing (2)

• .github/workflows/deploy-user-docker.yml (1 hunks)
• nowait-app-user-api/src/main/java/com/nowait/ApiUserApplication.java (0 hunks)

Walkthrough

이번 변경사항은 GitHub Actions 워크플로우 파일에서 파일 복사 단계의 소스 파일 지정 방식을 YAML 리스트에서 멀티라인 문자열 블록 스칼라로 수정하였고, Java 엔트리포인트 파일의 마지막 공백 줄을 제거했습니다. 코드 로직에는 영향이 없습니다.

Changes

Cohort / File(s)	Change Summary
GitHub Actions 워크플로우 포맷 변경 .github/workflows/deploy-user-docker.yml	SCP 액션의 source 입력값을 YAML 리스트에서 멀티라인 문자열 블록 스칼라(`
Java 파일 포맷팅 nowait-app-user-api/src/main/java/com/nowait/ApiUserApplication.java	파일 마지막의 불필요한 공백 줄 제거. 코드 로직에는 영향 없음.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• refactor: 배포 스크립트 수정 #87: 두 PR 모두 GitHub Actions 배포 워크플로우에서 EC2로 파일을 전송하는 SCP 단계의 파일 지정 방식을 수정합니다.
• refactor: deploy-user-docker.yml 수정 및 배포 테스트 진행 #99: 두 PR 모두 deploy-user-docker.yml 파일 내 SCP 액션의 소스 파일 지정 방식을 다루지만, 한쪽은 포맷(리스트→멀티라인), 다른 한쪽은 경로 자체를 수정합니다.
• chore: user CI/CD 스크립트 수정 #27: 두 PR 모두 ApiUserApplication.java 파일의 마지막 공백 줄 추가/삭제와 같은 사소한 포맷팅 변경만 포함합니다.

Suggested reviewers

• HyemIin

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/#206-prometheus-grafana

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.