The 42d054b file-replace pattern is fine for release snapshots, but it discards line-level history at every release, by moving a file to a new subdirectory, and adding a whole new file at the root.
A more diff-friendly convention would be:
- To eep one canonical filename (e.g.,
codebook_airwars_latest.csv) for incremental edits, so every commit is a real diff.
- On release, copy the canonical file into versions/codebook_airwars_.csv in the same commit — that preserves both the snapshot and the diff (Git will record a Copy similarity, not a Rename).
- The current dated-filename convention can stay as the display name in the README, but the source of truth in repo should be stable.
Which would look like this:
The 42d054b file-replace pattern is fine for release snapshots, but it discards line-level history at every release, by moving a file to a new subdirectory, and adding a whole new file at the root.
A more diff-friendly convention would be:
codebook_airwars_latest.csv) for incremental edits, so every commit is a real diff.Which would look like this: