[All-Chore] 워크플로우 트리거 추가 및 프론트엔드 스크립트 잘못된 경로 수정

[hamo-o]

#️⃣ 연관된 이슈>

• [FE-Fix] ENV 인식 문제 해결 및 배포 스크립트 수정 #413

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

• FE, BE 워크플로우 파일 수정 시에도 CI/CD가 돌도록 합니다.
• 프론트엔드 스크립트에서 잘못된 경로로의 파일 복사를 수정합니다.
• .env 파일은 빌드 시점에만 사용되므로, 복사하는 내용을 삭제합니다. (이전 PR에서 vite 관련 설정만으로 해결되었음)

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

진짜 끝..

Summary by CodeRabbit

• Chores
  • Updated deployment and CI workflows to trigger when workflow files themselves are modified.
  • Adjusted frontend deployment process by removing the step that copies the .env file and changing the deployment target directory for built files.

[coderabbitai]

Walkthrough

The GitHub Actions workflow files for backend and frontend CI/CD were updated to ensure that changes to their respective workflow files themselves will trigger the workflows. Additionally, the frontend deployment workflow was modified to remove the .env file copying step and to change the deployment target directory on the EC2 instance.

Changes

File(s)	Change Summary
.github/workflows/be-cd.yml	Added the workflow file itself to the trigger paths for backend CD on push to dev/main.
.github/workflows/be-ci.yml	Included the workflow file itself in the trigger paths for backend CI on PRs to dev.
.github/workflows/fe-cd.yml	Added the workflow file itself to trigger paths, removed .env copy step, changed deploy directory.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub
    participant EC2

    Developer->>GitHub: Push/PR (including workflow file changes)
    GitHub->>GitHub Actions: Trigger CI/CD workflow
    alt Frontend CD
        GitHub Actions->>GitHub Actions: Build frontend
        GitHub Actions-->>GitHub Actions: Skip .env copy
        GitHub Actions->>EC2: Copy built files to ~/app
    else Backend CD/CI
        GitHub Actions->>GitHub Actions: Run backend workflow
    end

Loading

Poem

In the warren of code, the workflows hop,
Now they trigger themselves—no need to stop!
Frontend files leap to a brand new home,
No .env to carry, just pure code to roam.
With every push and pull, the actions align,
The rabbits of CI/CD keep it all in line! 🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6c939ed and ed7f9da.

📒 Files selected for processing (3)

• .github/workflows/be-cd.yml (1 hunks)
• .github/workflows/be-ci.yml (1 hunks)
• .github/workflows/fe-cd.yml (2 hunks)

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

🪧 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? Join our Discord community 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 sequence diagram to generate a sequence diagram of the changes in 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.

[kwon204]

고생하셨습니다!