Skip to content

Document deploying from GitHub Actions - #5

Open
lnsp wants to merge 1 commit into
masterfrom
github-actions-page
Open

lnsp wants to merge 1 commit into
masterfrom
github-actions-page

Conversation

@lnsp

@lnsp lnsp commented Nov 20, 2026

Copy link
Copy Markdown
Member

What

  • New page, "Deploying from GitHub Actions" (advanced-topics/github-actions.md), added to the sidebar under "Advanced concepts". It covers:
    • setup: .valar.yml, a token from the console stored as the VALAR_TOKEN secret, and the workflow;
    • pinning by commit;
    • inputs and outputs;
    • build-only pull request checks;
    • pull request previews and their limits (no forks, never pull_request_target, previews are disabled rather than deleted, and the token's reach);
    • the CLI's VALAR_TOKEN/VALAR_ENDPOINT/VALAR_PROJECT for other CI systems.
  • "Publishing the service" now uses the current CLI commands: valar build push --wait, valar build list and valar service url. It used the 2.x ones (valar push, valar builds, valar list). It also links to the new page.
  • App.test.tsx: the page before /stacks in the previous/next links is now the new page.

It documents valar/action v3.0.0 and CLI 4.7.0, both released.

Testing

npm test (39 tests, including the link, anchor and sidebar checks), npm run lint, npm run typecheck and npm run build all pass. The new page is prerendered at dist/advanced-topics/github-actions/index.html.

Adds a page on valar/action v3: setup, inputs and outputs, build-only
pull request checks, pull request previews and the CLI's environment
variables for other CI systems. The publishing guide uses the current CLI
commands (build push --wait, build list, service url) instead of the 2.x
ones.
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