teslasync/.gitattributes at main · ev-dev-labs/teslasync · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
# Vendored Tesla Fleet Telemetry protobuf — checksum-gated, byte-exact.
# See api/proto/tesla/SOURCE.md.
api/proto/tesla/vehicle_data.proto binary

# i18n catalogue — additive key-union merge so parallel workers that each
# add different translation keys never hard-conflict. The `jsonunion` driver
# (git config merge.jsonunion.driver) runs merge-json-union.mjs, which unions
# keys from both sides instead of taking one wholesale. Without this wiring a
# single en.json key collision would stall a whole shard in the elevation loop.
web/src/i18n/en.json merge=jsonunion

# Generated Go files emitted by cmd/protogen-tesla — written with LF.
# Without this, autocrlf=true on Windows rewrites them to CRLF on
# checkout, which makes `git status` report them as modified after
# every `go generate` and trips the phase-42 prompt 0015 drift gate.
internal/tesla/protomodel/*_gen.go text eol=lf
cmd/protogen-tesla/testdata/golden/*_gen.go text eol=lf

# Phase A2.3 (chore/repo-reorganization) — defend against Windows
# CRLF artifacts in text source files. The repo is gofmt-clean on
# Linux (where CI runs), but Windows checkouts with the default
# PowerShell Out-File behaviour, and any Windows IDE/tool that writes
# without explicitly opting into LF, would leave the working tree in
# CRLF while the blob stays LF. That made `gofmt -l` falsely report
# ~900 "needing formatting" because gofmt reads CRLF from disk and
# writes LF. Forcing eol=lf on every text source language we ship
# eliminates the false positive without touching the blobs.
*.go         text eol=lf
*.mod        text eol=lf
*.sum        text eol=lf
*.ts         text eol=lf
*.tsx        text eol=lf
*.js         text eol=lf
*.jsx        text eol=lf
*.mjs        text eol=lf
*.cjs        text eol=lf
*.json       text eol=lf
*.jsonc      text eol=lf
*.yml        text eol=lf
*.yaml       text eol=lf
*.toml       text eol=lf
*.md         text eol=lf
*.sql        text eol=lf
*.sh         text eol=lf
*.bash       text eol=lf
*.py         text eol=lf
*.patch      text eol=lf -whitespace
*.css        text eol=lf
*.scss       text eol=lf
*.html       text eol=lf
*.svg        text eol=lf
Makefile     text eol=lf
*.mk         text eol=lf
Dockerfile*  text eol=lf
.editorconfig text eol=lf
.gitignore   text eol=lf
.gitattributes text eol=lf
.env*        text eol=lf

# Windows-shipped artifacts: keep native line endings.
*.ps1        text eol=crlf
*.cmd        text eol=crlf
*.bat        text eol=crlf

# Pure binaries: never normalise.
*.png        binary
*.jpg        binary
*.jpeg       binary
*.gif        binary
*.ico        binary
*.webp       binary
*.woff       binary
*.woff2      binary
*.ttf        binary
*.eot        binary
*.pdf        binary
*.zip        binary
*.tar        binary
*.tar.gz     binary
*.gz         binary
*.exe        binary
*.dll        binary
*.so         binary
*.dylib      binary
# .proto files: marked binary so they stay byte-exact. The vendored
# Tesla proto at api/proto/tesla/vehicle_data.proto is also explicitly
# marked above (top of file) for clarity; the rule below covers the
# generic case for any other proto we may vendor.
*.proto      binary