I used to have the default branch checked out at the top-level and then have feature branches checked out in nested worktrees, but I found it annoying how the nested worktrees showed up as untracked files in the top-level worktree, figured a bare repo was cleaner.

Do you recall why someone on stackoverflow recommended against using a bare checkout? Was it just because some tooling might be expecting a .git dir? I find most tools use libgit or something similar, so it usually isn't an issue.

IDK if the sheer quantity of builds we're currently running in nixvim is contributing, but we're running into buildbot issues with cross-comp/available builders rather frequently, leading to us having to rebuild to get a green checkmark (putting even more strain on resources)...

e.g. this is from a recent build (from this eval):

Failed to find a machine for remote build!
derivation: ycm30n2fwjwycmx3hi21gvn1q4kr04yy-plugins-ui-zen-mode.drv
required (system, features): (aarch64-linux, [])
2 available machines:
(systems, maxjobs, supportedFeatures, mandatoryFeatures)
([aarch64-linux], 80, [benchmark, big-parallel, gccarch-armv8-a, kvm, nixos-test], [])
([aarch64-darwin, x86_64-darwin], 8, [big-parallel], [])
error: a 'aarch64-linux' with features {} is required to build '/nix/store/ycm30n2fwjwycmx3hi21gvn1q4kr04yy-plugins-ui-zen-mode.drv', but I am a 'x86_64-linux' with features {benchmark, big-parallel, kvm, nixos-test}