diff options
| author | Craig Jennings <c@cjennings.net> | 2026-08-20 00:15:19 -0700 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-08-20 00:15:19 -0700 |
| commit | a028aa589056167160b39cf9e023c12dd30dec34 (patch) | |
| tree | 50fa1120f4d9b7d9728898810b47c5ec1233cd27 /archsetup.conf.example | |
| parent | dc068cab17624721c274e6810391308a920f57af (diff) | |
| download | archsetup-a028aa589056167160b39cf9e023c12dd30dec34.tar.gz archsetup-a028aa589056167160b39cf9e023c12dd30dec34.zip | |
fix(installer): clone my working repos with full history
archsetup and dotfiles were cloned with --depth 1. They aren't build trees. They're the two repos I develop in on every machine this installs, and velox came back from its rebuild carrying 7 commits of history in each instead of 851.
A shallow clone degrades quietly. Past the graft point `git log -- <path>` answers "no commits" rather than failing, so a search of history for specific files came back empty and exited clean. The clone couldn't see the history they live in. Blame and bisect break the same way, less dangerously.
Dropping --depth also drops the implicit --single-branch, so both clones now fetch every branch. That's what I want in a repo I work in.
The AUR build clones stay shallow. They exist to run make install and are then discarded. A test asserts they keep --depth 1, so a broad sed can't take them along.
Diffstat (limited to 'archsetup.conf.example')
0 files changed, 0 insertions, 0 deletions