Add file and directory to be excluded from format updates

[hlts2]

Description

I changed to exclude from auto fomat because unnecessary PRs are created many times.

• Update license headers / Format codes #2541

Related Issue

Versions

• Go Version: 1.22.5
• Rust Version: 1.77.2
• Docker Version: 20.10.8
• Kubernetes Version: v1.30.3
• NGT Version: 2.2.3

Checklist

• I have read the CONTRIBUTING document and completed our CLA agreement.
• I have checked open Pull Requests for the similar feature or fixes?

Special notes for your reviewer

Summary by CodeRabbit

• Chores
  • Expanded the workflow configuration to include additional files for the formatting process, enhancing dependency management during formatting.

[coderabbitai]

Walkthrough

Walkthrough

The change enhances the .github/workflows/format.yml file by expanding the git checkout command to include additional files relevant to dependency management. This adjustment ensures that more configuration files are reverted to their last committed state during the formatting process, potentially improving the handling of dependencies in the workflow. The overall control flow remains unchanged, but the scope of affected files is broader.

Changes

Files	Change Summary
.github/workflows/format.yml	Expanded git checkout command to include additional files: ./example/client/go.mod, ./example/client/go.sum, and ./dockers.

Sequence Diagram(s)

sequenceDiagram
    participant Workflow
    participant Git
    participant Files

    Workflow->>Git: Execute git checkout
    Git->>Files: Revert to last committed state
    Files-->>Git: Return files
    Git-->>Workflow: Files ready for formatting
    Workflow->>Workflow: Continue with formatting process

Loading

---

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

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6ca9f1c and 12179c6.

Files selected for processing (1)

• .github/workflows/format.yml (1 hunks)

Additional comments not posted (1)

.github/workflows/format.yml (1)

62-62: Verify the necessity of additional files in git checkout.

The git checkout command has been expanded to include ./example/client/go.mod, ./example/client/go.sum, and ./dockers. Ensure that these files are necessary for the workflow and that their inclusion does not introduce any unintended side effects.

[vdaas-ci]

[CHATOPS:HELP] ChatOps commands.

• 🙆‍♀️ /approve - approve
• 🍱 /format - format codes and add licenses
• ✅ /gen-test - generate test codes
• 🏷️ /label - add labels
• 🔚 2️⃣ 🔚 /label actions/e2e-deploy - run E2E deploy & integration test

[vdaas-ci]

[FORMAT] Failed to format.