Skip to content

Add local bootstrap and use editorial validation in CI#1

Closed
ritorhymes wants to merge 2 commits into
eips-wg:masterfrom
ritovision:local-build-system
Closed

Add local bootstrap and use editorial validation in CI#1
ritorhymes wants to merge 2 commits into
eips-wg:masterfrom
ritovision:local-build-system

Conversation

@ritorhymes

@ritorhymes ritorhymes commented Apr 15, 2026

Copy link
Copy Markdown

Important

This PR is part of the coordinated multi-repo local build system series tracked in preprocessor#8. It is intended to land in coordination with preprocessor#9, EIPs#10, and ERCs#10. This PR depends on preprocessor#9 being merged and released first. Until the released build-eips binary includes the new editorial command surface, CI for this PR is expected to fail.

Description

This PR adds the template-side wiring for the local multi-repo build system.

In this repo, that means adding the checked-in local bootstrap entrypoint and aligning automation with the explicit build-eips command surface introduced in preprocessor#9. This mirrors the same repo-local wiring added in the corresponding EIPs and ERCs PRs.

Changes

  • add scripts/dev-setup as the checked-in local workspace bootstrap helper
  • update contributor guidance to point at the canonical local workspace guide
  • switch CI to explicit editorial validation through build-eips editorial
  • keep publish on the site build path

Validation

Template contains no proposal content, so editorial validation was exercised from the rewritten EIPs and ERCs branches using a build-eips binary built from preprocessor#9.

Those branches were verified with:

  • build-eips --staging editorial build --against-upstream --format github
  • build-eips --staging build

Add a checked-in `scripts/dev-setup` entrypoint for the local
multi-repo workflow.

The helper locates or installs `build-eips` and `just`,
initializes the workspace, refreshes the generated helpers, and
prints the next useful commands.

Update the contributor guidance to point at the canonical local
workspace guide.
Run proposal validation through the explicit editorial command
surface in CI.

Keep the publish workflow on the site build path so site builds
and editorial validation remain separate in automation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant