Repository navigation
Expand file tree
/
Copy path.gitattributes
More file actions
45 lines (38 loc) · 2.19 KB
/
Copy path.gitattributes
File metadata and controls
45 lines (38 loc) · 2.19 KB
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
# Code-generated reference docs are emitted with LF by `gen_docs`. Pin them to
# LF on every platform so the docs-drift gate (`cargo test` + `gen_docs --check`)
# is byte-stable — Windows checkouts would otherwise convert them to CRLF and
# fail the comparison.
docs/reference/generated/*.md text eol=lf
# Registry snapshots are generated by `gen_registry` with LF and compared
# byte-for-byte in CI and lib tests (GH #726). Same rationale as the
# generated docs above.
rust/data/addon_registry.json text eol=lf
rust/data/grammar_registry.json text eol=lf
# The packaged capability registry is compared with the repository one as text
# (`product_capabilities::tests`, scripts/check-capabilities.py).
product/capabilities.toml text eol=lf
rust/data/product-capabilities.toml text eol=lf
# Signed release assets: the signatures cover the exact downloaded bytes, so a
# CRLF checkout on Windows would make genuine fixtures fail verification.
rust/src/core/updater/testdata/** -text
# The 3.11.0 migration journal fixtures (#2175): the receipt pins the SHA-256 of
# the pre-v4 config bytes, so a CRLF checkout on Windows reads as a tampered
# backup ("backup-mismatch").
rust/tests/fixtures/config_migration_v3_11_0/** -text
# Shipped database migrations are immutable: deployed databases recorded their
# bytes (ee/governance/migrations/legacy-history.txt). A whitespace "fix" changes
# the checksum, so `git diff --check` must not ask for one.
ee/governance/migrations/002_request_log.sql -whitespace
ee/governance/migrations/014_stripe_billing.sql -whitespace
# Derivations registry (scripts/derivations.py): generated files are regenerated
# and list files merge as line sets, so two branches never text-conflict on them.
# Needs `make setup-merge-drivers` (or `make setup`) once per clone; without it git
# falls back to its normal text merge. After a merge, run
# `python3 scripts/derivations.py regenerate` and commit what it rewrites.
CHANGELOG.md merge=leanctx-lineset
PUBLISH_MANIFEST.toml merge=leanctx-lineset
ee/delivery/FEATURE_SCOPE_REGISTER.csv merge=leanctx-lineset
frozen-hashes.json merge=leanctx-json
Cargo.lock merge=leanctx-cargolock
SBOM.cdx.json merge=leanctx-regenerate
THIRD_PARTY_NOTICES merge=leanctx-regenerate