Skip to content

Conversation

@kwon204
Copy link
Contributor

@kwon204 kwon204 commented Mar 23, 2025

#️⃣ 연관된 이슈>

📝 작업 내용> 이번 PR에서 작업한 내용을 간략히 설명해주세요(이미지 첨부 가능)

  • scp 스크립트 중 strip_components 옵션이 파일 경로 중 설정한 값만큼 삭제하는 거였습니다.

🙏 여기는 꼭 봐주세요! > 리뷰어가 특별히 봐주었으면 하는 부분이 있다면 작성해주세요

Summary by CodeRabbit

  • Chores
    • Updated the deployment configuration to adjust how file paths are structured during transfers.
    • Ensured that both backend and frontend deployments now place files correctly in the target environment.

@kwon204 kwon204 added this to the 7️⃣ 7차 스프린트 milestone Mar 23, 2025
@kwon204 kwon204 requested review from dioo1461, efdao and hamo-o March 23, 2025 16:18
@kwon204 kwon204 self-assigned this Mar 23, 2025
@coderabbitai
Copy link

coderabbitai bot commented Mar 23, 2025

Walkthrough

This pull request updates the GitHub Actions deployment workflows by modifying the strip_components parameter, which affects how many leading components of the source file paths are removed during the file copy to the EC2 instance. In the be-cd.yml file, the parameter is changed from 1 to 2. In the fe-cd.yml file, there are two updates: one step changes the value from 1 to 3 for copying Nginx files, and another from 1 to 2 for copying the frontend deployment script. There are no changes to exported or public declarations.

Changes

Files Change Summary
.github/workflows/be-cd.yml Updated strip_components from 1 to 2 for the "Copy deploy_script to EC2" step.
.github/workflows/fe-cd.yml Updated strip_components: changed from 1 to 3 for copying Nginx files and from 1 to 2 for copying the frontend deployment script.

Sequence Diagram(s)

sequenceDiagram
    participant GitHubActions as GitHub Actions
    participant DeployJob as Deployment Job
    participant EC2 as EC2 Instance

    GitHubActions->>DeployJob: Trigger deployment workflow
    DeployJob->>DeployJob: Determine strip_components for each file copy
    DeployJob->>EC2: Copy file(s) with adjusted path (stripping N components)
    EC2-->>DeployJob: Confirm file received and placed
    DeployJob-->>GitHubActions: Report job success
Loading

Possibly related PRs

Suggested reviewers

  • dioo1461
  • hamo-o
  • efdao

Poem

I'm a bouncy bunny in the code field,
Stripping paths with a joyful yield.
Two leaps and three hops, paths realigned,
Delivering files in perfect design.
With a twitch of my ears and whisker cheer,
I celebrate changes that now appear!
🐇💻✨


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
🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
.github/workflows/fe-cd.yml (1)

49-49: Confirm the correct stripping for Nginx files.
The strip_components value for copying Nginx files was updated from 1 to 3, which will remove three leading directory levels from the source path. Verify that this adjustment positions the Nginx configuration files correctly in the target directory on the EC2 instance.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9d3bedd and 1bf5a8c.

📒 Files selected for processing (2)
  • .github/workflows/be-cd.yml (1 hunks)
  • .github/workflows/fe-cd.yml (2 hunks)
🔇 Additional comments (2)
.github/workflows/be-cd.yml (1)

51-51: Verify the updated strip_components value.
The parameter has been updated from 1 to 2 in the "Copy deploy_script to EC2" step. This change should now remove two leading components from the source file path. Please ensure that the resulting file layout on the EC2 instance matches the intended structure.

.github/workflows/fe-cd.yml (1)

59-59: Validate the updated strip for the frontend deploy script.
Here, strip_components has been changed from 1 to 2 to ensure that extra directory levels are removed from the deploy script’s path. Please check that this modification results in the expected file structure on deployment.

Copy link
Collaborator

@efdao efdao left a comment

Choose a reason for hiding this comment

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

고생하셨습니다.

@kwon204 kwon204 merged commit 247697e into dev Mar 24, 2025
5 checks passed
@kwon204 kwon204 deleted the feature/be/moving branch March 24, 2025 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants