CONTRIBUTING: source and build output as two commits in one push (not two pushes), with the two exemptions
This commit is contained in:
parent
b799252425
commit
43130aa40e
1 changed files with 6 additions and 0 deletions
|
|
@ -53,6 +53,12 @@ it (script tag or the generated per-map page). Same-origin vs external-CDN modes
|
|||
- Never bake tokens or data into a bundle — everything arrives at runtime via `profile-config`.
|
||||
- Before a PR: `bun run build && bun run verify` must pass (adds drop-portability + parse gates).
|
||||
- Colors are values, not logic: [documentation/contributing/COLORS.md](./contributing/COLORS.md).
|
||||
- A landing that changes source AND its build output arrives as **two commits in one push**: the source
|
||||
change first, then a `rebuild <bundle>` commit carrying only `public/`. Reviewers read the first; the
|
||||
second is machine output. Don't split them across two pushes: the landing check rebuilds every affected
|
||||
bundle on the commit about to reach main and refuses one whose `public/` bundle no longer matches its
|
||||
source. Exempt: a `public/`-only rebuild after someone else's source landed, and a comment-only source
|
||||
change (comments are stripped from the build, so there is no `public/` half).
|
||||
|
||||
## One-line recap
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue