chore: configure git attributes and container deployment

[iplaylf2]

Summary by CodeRabbit

• Documentation

  • Added Windows-specific instructions for copying templates and handling symlinks
  • Added notes detailing symlink setup commands for Windows environments

• Chores

  • Updated line ending standardization for shell scripts
  • Enhanced development container configuration with support for local features
  • Updated Docker build path references

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Quick Notes

• Title: Set the PR title to @coderabbitai to have the bot generate one for you.

• Review: The bot reviews PRs by default. To opt out, add the no bot reviewer label.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR configures git attributes for line endings, updates documentation with Windows-specific deployment instructions, and modifies template container configurations including devcontainer features, dockerfile paths, and relative path references.

Changes

Cohort / File(s)	Summary
Git configuration .gitattributes	Added rule to enforce LF line endings for shell script files
Documentation README.md	Added Windows-specific instructions for template copying using robocopy and new Notes section covering symlink handling with enabling commands and recovery procedures
Template container configuration projects/.template/.devcontainer/devcontainer.json, projects/.template/.devcontainer/features, projects/.template/docker-compose.yaml, projects/.template/images	Updated devcontainer with features property, added relative path references for features and images directories, and changed dockerfile path from ../../images/base/Dockerfile to images/base/Dockerfile

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• PR #5: Modifies the same template devcontainer and docker-compose files with related changes to Dockerfile paths and devcontainer configuration
• PR #1: Adds the images/base/Dockerfile that the main PR references in updated path configurations
• PR #6: Updates identical template files with related changes to dockerfile paths and devcontainer features property

🚥 Pre-merge checks | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	PR description is a template placeholder requesting bot-generated title; lacks substantive information about actual changes.	Replace template text with actual PR description summarizing: symlink template setup, devcontainer features configuration, and Windows symlink documentation updates.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @projects/.template/.devcontainer/features:
- Line 1: The committed symlink named "features" inside the .devcontainer
directory points to a non-existent target ("../../../features"); fix it by
either updating that symlink's target to a valid existing directory in the repo
(adjust the relative path so it resolves from the .devcontainer folder to the
real features directory) or remove the symlink entirely if it’s not needed, then
stage and commit the corrected symlink object so the repository no longer
contains a broken link.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f104140 and fdb7ec0.

📒 Files selected for processing (6)

• .gitattributes
• README.md
• projects/.template/.devcontainer/devcontainer.json
• projects/.template/.devcontainer/features
• projects/.template/docker-compose.yaml
• projects/.template/images

🔇 Additional comments (6)

.gitattributes (1)

1-1: LGTM!

Enforcing LF line endings for shell scripts is a best practice for cross-platform compatibility and prevents execution issues on Unix-based systems.

README.md (2)

10-10: Clear Windows guidance added.

The inline reference to Windows robocopy instructions is helpful for Windows users.

---

16-31: Well-documented Windows symlink workflow.

The Notes section provides clear, step-by-step Windows-specific commands with appropriate robocopy flags (/E, /SL, /XC, /XN, /XO) to preserve symlinks while copying templates. The documentation is actionable and aligns with the PR's symlink-first approach.

projects/.template/docker-compose.yaml (1)

5-5: The dockerfile path change is valid and properly configured. The images symlink already exists at projects/.template/images -> ../../images, and the Dockerfile is correctly resolved through this symlink. No build failures or path resolution issues will occur.

projects/.template/.devcontainer/devcontainer.json (1)

3-6: The local features symlink is properly configured.

The symlink at projects/.template/.devcontainer/features correctly points to ../../../features and the target directory is accessible. Note that on Windows, developers must enable Developer Mode or have the appropriate permissions to work with symlinks; consider documenting this requirement if not already covered.

projects/.template/images (1)

1-1: No changes needed - Windows symlink documentation is already in place.

The symlink is correctly tracked by git and the Windows setup instructions are documented in the README.md "Symlinks" section, including the git config --local core.symlinks true command, git checkout -f for re-checkout, and robocopy for copying while preserving symlinks. The commit "docs: clarify Windows symlink workflow" has already addressed this documentation.