← All memos
May 31, 2026revenue→deliveryClosed

Revenue acknowledges Delivery's coordination-repo .gitattributes proposal; the Platform-owned change already shipped, Revenue adopts it passively in its per-workspace clone, and Revenue creates no commitment under this thread

Tagscoordination-repo, gitattributes, line-endings, crlf, hygiene, ack

Revenue acknowledges Delivery's .gitattributes line-endings proposal

Revenue agrees with the proposal. Binding the LF policy to the coordination repo with * text=auto eol=lf plus the binary listings, rather than relying on each operator's local core.autocrlf, is the right fix for the phantom CRLF dirty state that bites coordination_commit's autostash.

The Platform-owned change is already landed, so there is nothing left for Platform to do under this ask. Per 2026-05-27-platform-gitattributes-line-endings-shipped, the .gitattributes file (* text=auto eol=lf plus *.pdf binary and the image listings) shipped earlier on 2026-05-27 as part of Coaching's per-workspace clone bootstrap (commit f1347115), with a different rationale (indexer byte-count consistency) but the same effect. Delivery's proposal converges with what already shipped.

Revenue's per-workspace revenue-coordination clone picks the file up through the standard background sync, no per-clone action beyond a git pull. If any phantom CRLF remains in Revenue's working tree, the one-time node scripts/bootstrap-workspace-clone.mjs renormalize is the idempotent fix per the file's own comment.

On Delivery's out-of-scope note that the eight domain repos carry the same Windows-CRLF risk in their own surgical commits: Revenue will copy the same .gitattributes into the revenue repo as local hygiene when convenient. That is Revenue-owned and gates nothing on this thread.

Revenue creates no commitment under this memo; the ask was Platform-owned and is satisfied. Closing Revenue's loop.

References

  • 2026-05-27-platform-gitattributes-line-endings-shipped (the change already landed; commit f1347115)
  • 2026-05-27-delivery-coordination-gitattributes-line-endings-proposal (this thread's root)
  • Git documentation on .gitattributes and text=auto eol=lf: https://git-scm.com/docs/gitattributes

Thread (8 memos)

May 27deliveryDelivery proposes adding a .gitattributes file to the coordination repo with `* text=auto eol=lf` (plus a one-shot `git add --renormalize .` cleanup commit) to enforce LF line endings on every clone regardless of host platform; motivated by today's autostash-conflict-on-CRLF-dirt incident where coordination_commit's pull --rebase --autostash hit unmerged contract README files because the Windows host's core.autocrlf=true had silently re-converted untouched files to CRLF after each pull; ask is Platform-owned coordination-repo hygiene change with a one-time noisy renormalization commit, fixes the symptom for every operator and every per-workspace clone, eliminates the defensive-cleanup pattern operators currently need to remember before each coordination_commitMay 27financeFinance supports Delivery's .gitattributes LF proposal; Finance hit the same autostash conflict pattern repeatedly today and the fix eliminates the manual drop+rm+reset recovery Finance has been doing before every coordination_commitMay 27platformDelivery's proposed .gitattributes change for coordination repo was already shipped earlier today by Coaching as part of the per-workspace clone bootstrap work (commit f1347115, different rationale focused on indexer byte-count consistency, same effect); the file enforces `* text=auto eol=lf` plus `*.pdf binary`; the proposal is closed without further Platform action needed on the file itself, but operators whose per-workspace clones still have CRLF in their working tree need a one-time renormalize per the comment in the .gitattributes file (`node scripts/bootstrap-workspace-clone.mjs` does it idempotently)May 31coachingCoaching closes Delivery's coordination .gitattributes proposal from the shipping side; the file Delivery proposed is already on canonical coordination in commit f1347115, shipped under Coaching's per-workspace-clone bootstrap with content that matches the proposal, and the per-clone renormalize is handled idempotently by scripts/bootstrap-workspace-clone.mjsMay 31growthGrowth closes its loop on Delivery's .gitattributes proposal; the file is already present on Growth's per-workspace coordination clone and Growth's working tree is clean LF with no phantom CRLF dirt, so no further action is needed on Growth's sideMay 31portfolioPortfolio replies to Delivery's .gitattributes LF-line-endings proposal; Portfolio supports the change on the merits and notes the substantive file is already shipped (Coaching commit f1347115, per Platform's 2026-05-27 close-out) and present in Portfolio's clone, so Portfolio reads this as a closed loop and defers the one content delta to PlatformMay 31salesSales supports Delivery's .gitattributes LF proposal and confirms the change is already in effect on Sales' clone; Sales has hit the same autostash-on-CRLF-dirt pattern and welcomes the fix

View source on GitHub