The contributor setup section instructs new contributors to run basectl setup --profile dev and then env -u BASE_HOME ./bin/base-test, but never mentions that the full test suite requires a sibling base-bash-libs checkout at ~/work/base-bash-libs. Without it, Base cannot resolve BASE_BASH_LIBS_DIR at runtime bootstrap, so every BATS test fails. The testing.md doc mentions this in passing, but CONTRIBUTING.md is the authoritative contributor onboarding path.
Fix: Add an explicit step before basectl setup --profile dev:
git clone https://github.com/basefoundry/base-bash-libs.git ~/work/base-bash-libs
with one sentence explaining that Base resolves reusable Bash libraries from a sibling checkout during source development.
File: CONTRIBUTING.md
The contributor setup section instructs new contributors to run
basectl setup --profile devand thenenv -u BASE_HOME ./bin/base-test, but never mentions that the full test suite requires a siblingbase-bash-libscheckout at~/work/base-bash-libs. Without it, Base cannot resolveBASE_BASH_LIBS_DIRat runtime bootstrap, so every BATS test fails. The testing.md doc mentions this in passing, but CONTRIBUTING.md is the authoritative contributor onboarding path.Fix: Add an explicit step before
basectl setup --profile dev:with one sentence explaining that Base resolves reusable Bash libraries from a sibling checkout during source development.
File:
CONTRIBUTING.md