docs(mesh): record why * -text is in GITATTRIBUTES - #218
Conversation
Git for Windows ships core.autocrlf=true at the SYSTEM level, so without this line a Windows peer gets CRLF working-tree checkouts of every note. omind writes LF everywhere, so the vault would disagree with itself: note_version digests are raw-byte hashes and would differ across the fleet for identical notes, and every index on that peer would rebuild. The line has been doing that job silently since mesh init was written. Deleting it breaks nothing on Linux or macOS, which is exactly what makes it easy to delete during a tidy-up. Found while validating v8.1.0 on a real Windows guest — `git config --system --get core.autocrlf` returns true there out of the box. Co-Authored-By: Claude Opus 5 <[email protected]>
|
Warning Review limit reached
Next review available in: 49 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
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. Comment |
1 participant
Comment-only. No version bump — ships alongside v8.1.1.
Why
While validating v8.1.0 on the Win11 guest I confirmed Git for Windows sets
core.autocrlf=trueat the system level:Without
* -textin the vault's.gitattributes, a Windows mesh peer would check out every note with CRLF. omind writes LF on every platform since v8.1.0, so the vault would disagree with itself:note_versionis a raw-byte digest, so identical notes would hash differently across the fleet,* -textdisables git's translation repo-wide and overridesautocrlf. It has been quietly doing that sincemesh initwas written, and nothing said so.Deleting it breaks nothing on Linux or macOS — which is precisely what makes it a tempting line to tidy away. The comment exists to make the next person hesitate.
Not a behaviour change
GITATTRIBUTEScontent is byte-identical; only the module comment above it changed.mesh initwrites the same file, andtest_mesh.py(33 tests) is unaffected.🤖 Generated with Claude Code