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

format.yml #23

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

format.yml #23

wants to merge 2 commits into from

Conversation

Est-1y
Copy link
Collaborator

@Est-1y Est-1y commented Sep 2, 2024

Summary by CodeRabbit

  • New Features

    • Introduced an automated GitHub Actions workflow for formatting Rust code, ensuring consistent code style across the repository.
  • Improvements

    • The workflow flags any unformatted code and commits formatted changes automatically, enhancing code quality management.

Copy link

coderabbitai bot commented Sep 2, 2024

Walkthrough

A new GitHub Actions workflow named "Format Rust Code" has been added to automate the formatting of Rust code in the repository. This workflow triggers on pull requests to the main branch, checking out the code, installing the Rust toolchain and rustfmt, formatting the code, and ensuring consistency by committing any changes.

Changes

Files Change Summary
.github/workflows/format.yml New workflow for formatting Rust code on pull requests.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub Actions
    participant Rust Toolchain
    participant Repository

    Developer->>GitHub Actions: Create pull request
    GitHub Actions->>Repository: Checkout code
    GitHub Actions->>Rust Toolchain: Install stable Rust
    GitHub Actions->>Rust Toolchain: Install rustfmt
    GitHub Actions->>Rust Toolchain: Run cargo fmt --all
    GitHub Actions->>Repository: Check for changes
    alt Changes found
        GitHub Actions->>Developer: Notify about formatting issues
    else No changes
        GitHub Actions->>Repository: Commit and push formatted code
    end
Loading

Poem

🐇 In the meadow where code does play,
A formatting friend has come to stay.
With rust and care, it tidies the night,
Making all snippets look just right!
Hooray for the workflow, so clever and neat,
Now our code dances on happy feet! 🌼


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.
Early access features: disabled

We are currently testing the following features in early access:

  • Anthropic claude-3-5-sonnet for code reviews: Anthropic claims that the new Claude model has stronger code understanding and code generation capabilities than their previous models. Note: Our default code review model was also updated late last week. Please compare the quality of the reviews between the two models by toggling the early access feature.

Note:

  • You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.
  • Please join our Discord Community to provide feedback and report issues on the discussion post.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 39a5360 and 32755e7.

Files selected for processing (1)
  • .github/workflows/format.yml (1 hunks)
Additional context used
actionlint
.github/workflows/format.yml

15-15: the runner of "actions/checkout@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


18-18: the runner of "actions-rs/toolchain@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

fmt:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
Copy link

Choose a reason for hiding this comment

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

Update the version of the actions/checkout action.

The v2 version of the actions/checkout action is too old to run on GitHub Actions.

Update the version to v3 to fix this issue:

-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3
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
- uses: actions/checkout@v2
- uses: actions/checkout@v3
Tools
actionlint

15-15: the runner of "actions/checkout@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

- uses: actions/checkout@v2

- name: Install Rust toolchain
uses: actions-rs/toolchain@v1
Copy link

Choose a reason for hiding this comment

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

Update the version of the actions-rs/toolchain action.

The v1 version of the actions-rs/toolchain action is too old to run on GitHub Actions.

Update the version to v2 to fix this issue:

-        uses: actions-rs/toolchain@v1
+        uses: actions-rs/toolchain@v2

Committable suggestion was skipped due to low confidence.

Tools
actionlint

18-18: the runner of "actions-rs/toolchain@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

@Est-1y Est-1y changed the title Create format.yml format.yml Sep 2, 2024
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: 2

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 32755e7 and 8ba47e0.

Files selected for processing (1)
  • .github/workflows/format.yml (1 hunks)
Additional context used
actionlint
.github/workflows/format.yml

12-12: the runner of "actions/checkout@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


17-17: the runner of "actions-rs/toolchain@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


29-29: workflow command "set-output" was deprecated. use echo "{name}={value}" >> $GITHUB_OUTPUT instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

(deprecated-commands)


29-29: workflow command "set-output" was deprecated. use echo "{name}={value}" >> $GITHUB_OUTPUT instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

(deprecated-commands)


38-38: "github.head_ref" is potentially untrusted. avoid using it directly in inline scripts. instead, pass it through an environment variable. see https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions for more details

(expression)

Additional comments not posted (2)
.github/workflows/format.yml (2)

12-12: The existing comment suggesting to update the version of the actions/checkout action to v3 is still valid and applicable to the current code segment.

Tools
actionlint

12-12: the runner of "actions/checkout@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


17-17: The existing comment suggesting to update the version of the actions-rs/toolchain action to v2 is still valid and applicable to the current code segment.

Tools
actionlint

17-17: the runner of "actions-rs/toolchain@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

Comment on lines +29 to +34
run: |
if [ -n "$(git status --porcelain)" ]; then
echo "::set-output name=needs_commit::true"
else
echo "::set-output name=needs_commit::false"
fi
Copy link

Choose a reason for hiding this comment

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

Replace the deprecated set-output workflow command.

The set-output workflow command is deprecated and should be replaced with echo "{name}={value}" >> $GITHUB_OUTPUT.

Apply this diff to fix the issue:

-          if [ -n "$(git status --porcelain)" ]; then
-            echo "::set-output name=needs_commit::true"
-          else
-            echo "::set-output name=needs_commit::false"
-          fi
+          if [ -n "$(git status --porcelain)" ]; then
+            echo "needs_commit=true" >> $GITHUB_OUTPUT
+          else
+            echo "needs_commit=false" >> $GITHUB_OUTPUT
+          fi
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
run: |
if [ -n "$(git status --porcelain)" ]; then
echo "::set-output name=needs_commit::true"
else
echo "::set-output name=needs_commit::false"
fi
run: |
if [ -n "$(git status --porcelain)" ]; then
echo "needs_commit=true" >> $GITHUB_OUTPUT
else
echo "needs_commit=false" >> $GITHUB_OUTPUT
fi
Tools
actionlint

29-29: workflow command "set-output" was deprecated. use echo "{name}={value}" >> $GITHUB_OUTPUT instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

(deprecated-commands)


29-29: workflow command "set-output" was deprecated. use echo "{name}={value}" >> $GITHUB_OUTPUT instead: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions

(deprecated-commands)


- name: Commit and Push Changes
if: steps.check_diff.outputs.needs_commit == 'true'
run: |
Copy link

Choose a reason for hiding this comment

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

Avoid using github.head_ref directly in inline scripts.

Using github.head_ref directly in inline scripts is potentially untrusted and should be avoided. Pass it through an environment variable instead for security hardening.

Apply this diff to fix the issue:

-        if: steps.check_diff.outputs.needs_commit == 'true'
+        if: steps.check_diff.outputs.needs_commit == 'true'
+        env:
+          HEAD_REF: ${{ github.head_ref }}
         run: |
           git config --local user.name "github-actions"
           git config --local user.email "[email protected]"
           git add -A
           git commit -m "Format code using rustfmt"
-          git push origin ${{ github.head_ref }}
+          git push origin $HEAD_REF

Committable suggestion was skipped due to low confidence.

Tools
actionlint

38-38: "github.head_ref" is potentially untrusted. avoid using it directly in inline scripts. instead, pass it through an environment variable. see https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions for more details

(expression)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant