Skip to Content
Welcome to RitoSwap's documentation!
CI / CDManual Workflows

Manual Workflows

All manual workflows are triggered via workflow_dispatch in GitHub Actions. They are used for one-off deploys or targeted test runs without waiting for the full pipeline.

WorkflowWhat it doesEnvironment
Manual - Deploy TestnetPrebuilt Vercel deploy for the DApptestnet
Manual - Deploy MainnetPrebuilt Vercel deploy for the DAppmainnet
Manual - Deploy DocsPrebuilt Vercel deploy for docs (local build)docs
Manual - Deploy StorybookBuild Storybook and deploy with Vercel CLIstorybook
Manual - ESLintRun ESLint for the dapp workspacen/a
manual-vitest-testsRun Vitest tests without Codecovn/a
manual-vitest-tests-codecovRun Vitest tests with Codecov uploadn/a
Manual - Hardhat TestsCompile and test smart contractsn/a
Manual - Pre-deploy E2ELocal build + Playwright smoke tests with Postgres servicen/a
Manual - Smoke E2EPlaywright smoke tests against testnettestnet
Manual - Smoke APISupertest API smoke tests against testnettestnet

Mirror dispatch workflows

The public mirror repo (https://github.com/ritovision/ritoswap-mirror) includes wrapper workflows that can be triggered manually when we want to run the private pipelines.

  • Dispatch DApp (dispatch-dapp.yml) -> pipeline-dapp.yml
  • Dispatch Docs & Storybook (dispatch-docs-storybook.yml) -> pipeline-docs-storybook.yml

These wrappers use the ci-dispatch environment and the RITOSWAP_PAT secret in the mirror repo.

Manual deploys reuse the same Vercel secrets as the pipelines. Test workflows rely on the same TEST_BASE_URL, CHAIN_ID, and auth-related vars described in the environments page.

⚠️

The manual-vitest-tests-codecov workflow requires CODECOV_TOKEN when Codecov enforces tokens (for example, protected branches).

Last updated on

RitoSwap Docs does not store, collect or access any of your conversations. All saved prompts are stored locally in your browser only.