Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ci] release 워크플로 수정 #148

Merged
merged 3 commits into from
Dec 21, 2024
Merged

[ci] release 워크플로 수정 #148

merged 3 commits into from
Dec 21, 2024

Conversation

EATSTEAK
Copy link
Owner

@EATSTEAK EATSTEAK commented Dec 21, 2024

What's in this pull request

  • release 워크플로가 동작하지 않는 문제 수정

Summary by CodeRabbit

  • Chores
    • Simplified caching mechanisms in build and lint workflows.
    • Added a condition to the release workflow to trigger only on changes to the Cargo.toml file.

@EATSTEAK EATSTEAK added bug Something isn't working ci Issues/changes for continuous intergrations labels Dec 21, 2024
@EATSTEAK EATSTEAK self-assigned this Dec 21, 2024
Copy link

coderabbitai bot commented Dec 21, 2024

Warning

Rate limit exceeded

@EATSTEAK has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 17 minutes and 49 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 3c55667 and 6b3204e.

📒 Files selected for processing (2)
  • .github/workflows/release-ios.yml (1 hunks)
  • .github/workflows/release.yml (1 hunks)

Walkthrough

The pull request focuses on modifying GitHub Actions workflow configurations across three files: build_test.yml, lint.yml, and release.yml. The primary changes involve simplifying caching mechanisms by removing cache-group parameters and adding a path filter for the release workflow. These modifications aim to streamline the CI/CD process by refining workflow triggers and caching strategies.

Changes

File Change Summary
.github/workflows/build_test.yml Removed with block and cache-group: build from the "Retrieve cache" step
.github/workflows/lint.yml Deleted cache-group: build parameter in the caching step
.github/workflows/release.yml Added paths filter to trigger workflow only on Cargo.toml changes and removed with clause in cache retrieval step

Possibly related PRs

Suggested labels

enhancement

Poem

🐰 Workflows dancing, cache lines clean,
Trimming the fat from our CI routine,
Cargo.toml triggers, a selective embrace,
Efficiency hopping at a rabbit's pace!
Build, test, release - streamlined and bright! 🚀


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
🪧 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. (Beta)
  • @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.

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: 1

🔭 Outside diff range comments (1)
.github/workflows/release.yml (1)

Line range hint 18-42: Consider optimizing version check and token usage

A few suggestions for improving this section:

  1. Consider using gh api repos/:owner/:repo/releases/latest instead of fetching all releases and taking the first one
  2. Consider using different tokens for checkout vs API operations (principle of least privilege)

Here's an optimized version of the version check:

      - name: Fetch latest release tag
        id: latest_release
        run: |
          curl -L \
            -H "Accept: application/vnd.github+json" \
-           -H "Authorization: Bearer ${{ secrets.IOS_GITHUB_TOKEN }}" \
+           -H "Authorization: Bearer ${{ secrets.GITHUB_TOKEN }}" \
            -H "X-GitHub-Api-Version: 2022-11-28" \
-           https://api.github.com/repos/EATSTEAK/rusaint/releases \
-           | jq '.[0].tag_name | "result=" + .' \
+           https://api.github.com/repos/EATSTEAK/rusaint/releases/latest \
+           | jq '.tag_name | "result=" + .' \
            | tr -d '"' >> $GITHUB_OUTPUT
🧰 Tools
🪛 yamllint (1.35.1)

[warning] 3-3: truthy value should be one of [false, true]

(truthy)


[error] 5-5: too many spaces inside brackets

(brackets)


[error] 5-5: too many spaces inside brackets

(brackets)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6014f76 and 3c55667.

📒 Files selected for processing (3)
  • .github/workflows/build_test.yml (0 hunks)
  • .github/workflows/lint.yml (0 hunks)
  • .github/workflows/release.yml (1 hunks)
💤 Files with no reviewable changes (2)
  • .github/workflows/build_test.yml
  • .github/workflows/lint.yml
🔇 Additional comments (1)
.github/workflows/release.yml (1)

Line range hint 52-53: LGTM! Cache configuration simplification

The removal of explicit cache configuration aligns with similar changes in other workflow files, simplifying the caching mechanism while maintaining functionality.

🧰 Tools
🪛 yamllint (1.35.1)

[warning] 3-3: truthy value should be one of [false, true]

(truthy)


[error] 5-5: too many spaces inside brackets

(brackets)


[error] 5-5: too many spaces inside brackets

(brackets)

Comment on lines 6 to 7
paths:
- './Cargo.toml'
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix the path filter syntax

The path filter syntax is incorrect. In GitHub Actions, paths should be specified relative to the repository root without leading ./.

Apply this diff to fix the path filter:

    paths:
-      - './Cargo.toml'
+      - 'Cargo.toml'
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
paths:
- './Cargo.toml'
paths:
- 'Cargo.toml'

@EATSTEAK EATSTEAK merged commit 7a6e4a8 into dev Dec 21, 2024
2 checks passed
@EATSTEAK EATSTEAK deleted the ci/fix-release branch December 21, 2024 08:28
EATSTEAK added a commit that referenced this pull request Dec 21, 2024
* ci: fix release workflow syntax

* ci: no cache-group for build and lint workflows

* ci: fix Cargo.toml check in release workflows
EATSTEAK added a commit that referenced this pull request Dec 21, 2024
* ci: fix release workflow syntax

* ci: no cache-group for build and lint workflows

* ci: fix Cargo.toml check in release workflows
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ci Issues/changes for continuous intergrations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant