fix: Local Setup on Windows

[Rounak-stha]

This PR addresses #5420 . The setup issue was because of the line endings on the *-entrypoint.sh files. The linux containers expects LF as EOL but on windows on clone, git by default updates the line endings to CRLF.

For contributers with already a local copy, run the following:

git rm -rf --cached .         # Clean the index
git reset --hard HEAD         # Reset to last commit with revaluation as we cleared the index

Here's more info: https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings

Summary by CodeRabbit

• Chores
  • Updated the project configuration to ensure shell script files have consistent line endings across different operating systems, enhancing compatibility and reducing potential execution errors.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai[bot]]

Walkthrough

This change updates the .gitattributes file to specify that all shell script files (*.sh) should be treated as text files with line endings normalized to LF (Line Feed). This adjustment aims to ensure consistency in line endings across different operating systems, facilitating collaboration in a cross-platform environment.

Changes

File	Change Summary
.gitattributes	Added entry for *.sh to enforce text eol=lf

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant Git
    participant System

    Developer->>Git: Commits changes
    Git->>System: Normalizes line endings for *.sh
    System-->>Git: Line endings set to LF
    Git-->>Developer: Changes committed with normalized line endings

Poem

🐰 In the meadow, scripts do play,
With LF endings, they dance all day.
No more worries, no more strife,
Just happy bunnies, scripting life!
Hoppity hop, let the code flow,
Together we thrive, in a seamless show! 🌼

---

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