Skip to content

Cross-link activate.source setup boundary docs #998

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
codeforester merged 1 commit into from
Jun 22, 2026
+3 −0
Merged

Cross-link activate.source setup boundary docs #998

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/setup-hooks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,9 @@ Instead, use the typed contracts Base already understands:
`activate.source` is intentionally not a setup hook: it does not run during
`basectl setup`, `basectl check`, or `basectl doctor`, and it exists only for
shell state that must affect the activated interactive subshell.
See the `activate.source` field in [Architecture - Project Manifest](architecture.md#project-manifest)
for the full shell activation contract, including when it runs and its scope
relative to setup.

When a project needs a product-specific guided installer or imperative
bootstrap, that logic should live in the project repository, for example:
Expand Down
Loading