Skip to content

docs(codegen): codegen targets update the tree when reached as a dependency #130

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
raphaelvigee merged 1 commit into from
Oct 24, 2026
Merged

docs(codegen): codegen targets update the tree when reached as a dependency #130

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
8 changes: 8 additions & 0 deletions website/docs/concepts/codegen.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,6 +160,14 @@ declares both a directory output and a file inside it is valid.
Run `heph validate` in CI alongside `heph tool gen-gitignore` to ensure no two targets
compete for the same part of the source tree.

## Reached through a dependency

A codegen target updates the tree whenever it is part of the run — not only when
you name it. If `//app:bin` depends on `//fmt:generated`, running `//app:bin`
writes `fmt/generated.txt` too, and `--frozen` on a run that reaches a codegen
target verifies it the same way. The target is written once per run, however many
targets depend on it.

## Verifying the tree in CI: `--frozen`

Running a codegen target normally **writes** its outputs into the tree — `copy`
Expand Down
Loading