chore: github action 환경 설정

[haroya01]

PR 이슈번호

---

추가 되거나 변경된 내용

---

논의 해 볼 내용

---

래퍼런스

Summary by CodeRabbit

• Chores
  • Updated the CI/CD workflow for the develop branch to enhance version retrieval accuracy.
  • Added a command to list all tags and ensured all tags are fetched with the --force option.

[coderabbitai]

Warning

Rate limit exceeded

@haroya01 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 19 minutes and 15 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

Files that changed from the base of the PR and between b35b4fd and ea9fa73.

Walkthrough

The changes in the CI/CD workflow for the develop branch focus on improving the version retrieval process. The command for fetching tags has been updated to ensure all tags are retrieved, and the method for determining the current version has been modified to sort and retrieve the latest tag matching a specific pattern. The overall structure of the workflow remains intact, with no changes to the logic for version determination based on branches or commit messages.

Changes

File Path	Change Summary
.github/workflows/ci-cd-develop.yml	Updated git fetch --tags to git fetch --tags --force, modified version retrieval to sort and list tags matching 'v*', retained echo command for current version, no changes to deployment steps or public entity declarations.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant CI/CD Workflow
    participant Git
    participant Docker

    Developer->>CI/CD Workflow: Trigger build
    CI/CD Workflow->>Git: git fetch --tags --force
    Git-->>CI/CD Workflow: Fetch all tags
    CI/CD Workflow->>Git: List and sort tags matching 'v*'
    Git-->>CI/CD Workflow: Return latest version
    CI/CD Workflow->>Docker: Build and push image
    Docker-->>CI/CD Workflow: Confirm image pushed

Loading

🐇 In the meadow, the changes hop,
Versioning now won't stop!
Tags are fetched with great delight,
Sorting through them, oh what a sight!
CI/CD dances, builds anew,
A joyful workflow, fresh as dew! 🌼

---

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