Skip to Content
Welcome to RitoSwap's documentation!
CI / CDComposite Actions

Composite Actions

The workflows are built on a set of reusable composite actions under .github/actions. These actions keep the pipelines consistent and reduce duplication.

Build and setup

ActionPurposeKey inputs
setup-node-pnpmInstall Node.js and pnpm with cachingnode-version, pnpm-version, working-directory
install-depsRun pnpm install with optional workspace filterfilter, working-directory, frozen-lockfile

Mirror dispatch wrappers

The mirror repo uses actions/github-script@v7 to dispatch workflows in the private repo and wait for completion. These wrappers live in ritovision/ritoswap-mirror and target ritovision/ritoswap using a PAT stored in the ci-dispatch environment.

Lint and tests

ActionPurposeKey inputs
run-eslintRun ESLint with optional strict modeworking-directory, strict
run-vitest-testsRun Vitest coverage and optionally upload to Codecovworking-directory, upload-coverage, codecov-flags, codecov-token, database-url
run-hardhat-testsCompile and test smart contractsworking-directory
run-predeploy-e2ePrisma migrate + optional seed, build, Playwright smoke testsworking-directory, database-url
run-smoke-e2ePlaywright smoke tests against a live sitebase-url, private-key, test-pattern, project, workers
run-smoke-apiSupertest API smoke tests against a live sitebase-url, private-key, token-id, chain-id, enable-state-worker, ai-chat-requires-jwt

The predeploy E2E action assumes a Postgres service is available in the workflow. It sets a test-focused environment for the build and smoke tests, and installs Playwright browsers.

Deploy and rollback

ActionPurposeKey inputs and outputs
vercel-deployDeploy to Vercel in remote or prebuilt mode

Inputs: mode, production, vercel-token, vercel-org-id, vercel-project-id, working-directory
Outputs: previous-url, deployment-url

vercel-rollbackRollback to a previous production deploymentInputs: deployment-url, vercel-token, vercel-org-id, vercel-project-id
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.