Skip to main content
Use this workflow for code and documentation changes. For model, provider, pricing, organisation, or benchmark records, submit a catalog issue instead; no local setup is needed.

​
Set up your fork

Install Git, Node.js 22.12 or newer, and pnpm. Fork the Phaseo repository, then clone your fork and create a new branch:

​
Make and preview the change

See Repository structure for the relevant application or package. For Markdown-only edits, you can also use GitHub’s file editor and open a pull request there.
Follow the relevant AGENTS.md instructions. Keep secrets in local environment files and out of commits. Local app previews may require configured backend services and normal sign-in.

​
Validate your changes

Run the checks relevant to the files you changed. For documentation:
For web changes:
Run a production build for rendering or routing changes. API, SDK, and schema changes need their corresponding tests and generation steps. See the root contribution guide.

​
Open a pull request

Stage only the files you changed, use a descriptive commit message, and push your branch:
Open a pull request from your fork. Explain the problem, what changed, and which checks passed. Link related issues and include screenshots for visible UI changes. Address review feedback before merge; changes become live after the relevant deployment completes. Follow the Code of Conduct. For large or uncertain changes, discuss the proposal before writing code.
Last modified on October 18, 2026