Skip to content
Beskid Beskid

Beskid

Jump to a Beskid service

Beskid

Jump to a Beskid service

Set Up the Repository

This source setup does not install Beskid for an end user. Use the installation procedure for a supported release.

Create a repository checkout. Install Git and the pinned pnpm toolchain. Confirm which root or submodule owner accepts the change.

  1. From the superrepo root, run ./scripts/setup-environment.sh to initialize pinned submodules and install root packages.
  2. Inspect git status --short in the root.
  3. Inspect git status --short in the submodule that you will change.
  4. Run pnpm --dir site/website test for website guidance changes.
  5. Run the focused gate that the changed component documents.
  6. Run broader gates only when the change crosses a contract boundary.
  7. Edit public guidance in site/website/src/content/docs/.
  8. Use the owning generator for derived files; do not edit generated output.

The checkout contains the pinned submodule commits unless an owner made an intentional change. The focused gate passes and reports the changed component.

If a submodule has unrelated work, preserve it and contact the submodule owner. Do not reset unrelated dirty state. If package installation fails, verify pnpm and the root lockfile before you change dependencies.

Change the Standard or write Docs.