[Feature] why not use --depth=1 in bootstrap?

[dxcvvxd]

Problem

takes too long to clone vsapi, using --depth=1 (and also removing --quiet because again why are you using that) i managed to clone it way faster and nothing broke

Proposed change

add --depth=1 to scripts/bootstrap.sh (optionally remove --quiet because seeing progress is important for the ux)

Alternatives considered

.

Scope

• This does not change gameplay, balance, or add content.

[Zaldaryon]

We cannot use git clone --depth=1 for the compile targets because forks.json pins specific commit SHAs rather than branch tips.

A shallow clone only fetches the latest commit on the default branch. The checkout only succeeded in your test because vsapi's current HEAD coincidentally matches the commit pinned for 1.22.7 (63d33f7). As soon as upstream pushes a new commit, or whenever bootstrap builds against a prior release (such as 1.22.5's 324ccf9), git clone --depth=1 leaves the repository without the target commit. The subsequent git checkout "$ref" then fails immediately with fatal: reference is not a tree.

--depth=1 is already used for the reference repositories under ref/source/, where pinning to an exact historical commit is not a build blocker.

Regarding --quiet: Git prints clone progress to standard error. In automated build scripts, CI pipelines, and PowerShell wrappers, unbuffered progress counters clutter the output and trigger false-positive error alerts. The script already prints an explicit status line (Cloning <name> at <ref>) before each clone starts.