Pull Requests

Review backend changes before they merge into the project draft or become publishable.

Pull Requests

Pull Requests give teams a review path for Spala changes. Use them when a user or AI agent prepares backend changes that should be inspected before merging or publishing.

Spala Pull Requests screen showing review status, changed resources, comments, and actions
Pull Requests give AI and human changes a review path before they merge into the project draft.

What You Can Review

- Changed database tables and fields
- Updated functions and backend logic
- Endpoint method, path, auth, and response changes
- Scheduled or background task changes
- Trigger, channel, and agent changes when included in a PR
- Comments, approvals, and requested changes
- AI review comments and AI-generated fix PRs
- Draft, open, approved, merged, declined, and needs-rebase states

Review Workflow

Open Pull Requests

Use the Pull Requests screen from Advanced mode when changes need team review.

Inspect the diff

Review changed models, functions, endpoints, tasks, and comments before merging.

Use AI review when useful

Ask AI to review the PR for missing validation, broken assumptions, or obvious backend issues.

Approve, request changes, or merge

Merge approved work into the project draft, then publish when the live API should change.

Clean up old review work

Close, reopen, delete, or bulk-delete PRs when they are no longer needed.

Useful for agent work

Pull Requests are especially useful when an MCP agent or Copilot makes a broad change. They give humans a clear review point before anything becomes live.

Publish
/features/publish-export
Make reviewed changes live
Project Snapshots
/features/project-snapshots
Keep checkpoints around larger changes
MCP
/agents/mcp
Let agents work through the project MCP