fix: backend-cd.yml

[dlwldnjs1009]

변경 사항

be/** 브랜치에 push되었을 때는 트리거되지 않고, 오직 develop 브랜치에 push되거나 pull request가 생성될 때만 GitHub Actions가 실행되도록 수정

테스트 결과 (테스트를 했으면)

ex) 베이스 브랜치에 포함되기 위한 코드는 모두 정상적으로 동작해야 합니다. 결과물에 대한 스크린샷, GIF, 혹은 라이브 데모가 가능하도록 샘플API를 첨부할 수도 있습니다.

Summary by CodeRabbit

• Chores
  • Revised the automated deployment process by updating branch targeting. Now, backend changes trigger only from a dedicated, stable branch, streamlining operations and reducing unintended deployments. This enhancement improves the reliability and control of our release process without affecting the overall user experience.

[coderabbitai]

Walkthrough

This update modifies the branch specification for triggering the backend continuous deployment workflow. The push event is now limited to commits on the develop branch instead of any branch under the be/ prefix. The pull request trigger remains configured for both main and develop branches, and no changes have been made to the workflow's jobs or steps.

Changes

File	Change Summary
.github/workflows/backend-cd.yml	Restricted the push trigger from pattern 'be/**' branches to only the develop branch; pull_request trigger remains unchanged.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant GH as GitHub Actions
    participant Job as Deployment Job

    Dev->>GH: Push commit to branch "develop"
    GH-->>Job: Trigger deployment workflow

    Dev->>GH: Open pull request to "main" or "develop"
    GH-->>Job: Validate pull request conditions

Loading

Possibly related PRs

• be/feat: github actions 배포 설정 #220: Modified branch specifications for triggering the workflow in the same .github/workflows/backend-cd.yml file, indicating a direct relationship with this change.

Suggested reviewers

• kim1387
• BellYun
• Gwanghyeon-k
• jung2941
• ukongee
• YunJuwon0825
• lsh1215

Poem

In a garden of code where branches sway,
I hop on “develop” to light up the day.
No stray “be/**” here, just a single trail,
My tiny paws dance as deployments prevail.
CodeRabbit cheers with a hop and a twirl—
A whimsical dance in our Dev workflow world!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7f6b9ed and a311b6a.

📒 Files selected for processing (1)

• .github/workflows/backend-cd.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: deploy

🔇 Additional comments (2)

.github/workflows/backend-cd.yml (2)

4-6: Push Trigger Branch Restriction Update
The push trigger is now limited exclusively to the develop branch, which aligns with the PR objective of reducing unnecessary CI/CD executions. Please confirm that any deployments previously triggered for branches under be/** are intentionally being excluded.

---

7-10: Pull Request Trigger Confirmation
The pull request event remains configured for both main and develop branches. This setup correctly complements the push trigger update, ensuring that PRs originating from these key branches continue to run the workflow.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • 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.

[github-actions]

Code review by ChatGPT

[lsh1215]

확인완료