Enforce /scripts directory uses LF line endings on all systems

[rithviknishad]

Proposed Changes

• Enforce /scripts directory uses LF line endings on all systems

Merge Checklist

• Update docs in /docs
• Linting Complete

@ohcnetwork/care-backend-maintainers @ohcnetwork/care-backend-admins

Summary by CodeRabbit

• Documentation
  • Updated README.md to include a note on Windows compatibility with Docker Compose, emphasizing the need for LF line endings to ensure proper script functionality.
  • Added a command to disable automatic line ending conversion in Git for users experiencing issues.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes in this pull request involve updates to the .gitattributes and README.md files. The .gitattributes file now specifies that all files in the scripts directory should use line feed (LF) for end-of-line (EOL) handling, promoting consistency. The README.md file has been modified to include a note about Windows compatibility with Docker Compose, advising users to set line endings to LF to avoid issues with the docker-entrypoint.sh script.

Changes

File	Change Summary
.gitattributes	Added a line to enforce LF as the EOL character for files in the scripts directory.
README.md	Added a note about Windows compatibility with Docker Compose, advising LF line endings.

Poem

In scripts where endings must align,
LF is the choice, oh so fine.
For Docker on Windows, heed the call,
Set your line endings, avoid a fall.
A note in the README, clear and bright,
Guiding users to do what's right! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8cb5fd3 and 87ac04e.

📒 Files selected for processing (2)

• .gitattributes (1 hunks)
• README.md (0 hunks)

💤 Files with no reviewable changes (1)

• README.md

✅ Files skipped from review due to trivial changes (1)

• .gitattributes

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.58%. Comparing base (8cb5fd3) to head (87ac04e).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #2625   +/-   ##
========================================
  Coverage    69.58%   69.58%           
========================================
  Files          211      211           
  Lines        11875    11875           
  Branches      1201     1201           
========================================
  Hits          8263     8263           
  Misses        3246     3246           
  Partials       366      366           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.