Background
PR #120 introduced .gitattributes.template: a 29-line cross-platform baseline that consumer repos receive on first sync and own thereafter. Upstream's own root .gitattributes is still the original 2-line file pinning LF for *.tmpl and .githooks/*.
This is an inconsistency: upstream ships an opinionated baseline for consumers but does not adopt it itself.
Decision needed
Should upstream eat its own dogfood and replace its root .gitattributes with (or extend it toward) the template baseline?
Arguments for
- Consistency: upstream's recommended convention is the convention upstream itself uses.
- Catches regressions where an editor saves a synced file with the wrong line endings.
Arguments against
- Upstream's actual needs are narrower than a generic consumer: PowerShell-heavy, no
.bat/.cmd, no .cs/.ts/.py source files at present. The minimal 2-line file already handles upstream's real requirements.
- Adopting the full template would require a one-time
git add --renormalize . commit touching many files (mostly markdown and PowerShell), creating a noisy history blip with no behavioral change.
Recommendation
Skip. Close as wontfix after a maintainer signs off. Filed so the decision is explicit and traceable rather than lingering as an open implicit question.
Acceptance
- Maintainer decision recorded in this issue (either close
wontfix with rationale, or open a small PR adopting the baseline + renormalization commit).
Context
Spawned from PR #120 follow-up review.
Background
PR #120 introduced
.gitattributes.template: a 29-line cross-platform baseline that consumer repos receive on first sync and own thereafter. Upstream's own root.gitattributesis still the original 2-line file pinning LF for*.tmpland.githooks/*.This is an inconsistency: upstream ships an opinionated baseline for consumers but does not adopt it itself.
Decision needed
Should upstream eat its own dogfood and replace its root
.gitattributeswith (or extend it toward) the template baseline?Arguments for
Arguments against
.bat/.cmd, no.cs/.ts/.pysource files at present. The minimal 2-line file already handles upstream's real requirements.git add --renormalize .commit touching many files (mostly markdown and PowerShell), creating a noisy history blip with no behavioral change.Recommendation
Skip. Close as
wontfixafter a maintainer signs off. Filed so the decision is explicit and traceable rather than lingering as an open implicit question.Acceptance
wontfixwith rationale, or open a small PR adopting the baseline + renormalization commit).Context
Spawned from PR #120 follow-up review.