Code changes

When a request asks for code to be written, changed, fixed, reviewed or tested, Relay drafts a plan and asks for approval. Nothing is touched until you approve it.

What happens after you approve

1. Check the working copy. If a repo has uncommitted changes, the run refuses to start, so your own work is never mixed in. If you explicitly asked Relay to commit your changes first (“commit and continue”), it commits them on your branch as their own commit.
2. Branch. In each repo, Relay creates a branch named arkinsta/<slug>-<id> from your current branch.
3. Make the change. The Code model works in all the chosen repos at once. It can run the workspace’s checks while it works.
4. Check again. Relay runs the checks once more after the change, so the reply says truthfully whether they pass.
5. Commit. What changed in each repo is committed, except files that might hold secrets (.env, keys, credentials), which are never committed.
6. Switch back. Every repo goes back to its original branch, so your checkouts are as you left them.

The reply lists each repo’s branch and commit, and asks whether to push.

Pull requests

Approve the follow-up and Relay pushes each branch and opens a pull request with the GitHub CLI. With several repos, you get one pull request per repo. You need gh installed and signed in (gh auth login).

One job per repo

Code runs and saved actions share a queue: only one job at a time touches a given repo, so Relay never builds a repo while it’s editing it. A job that spans several repos waits for everything queued earlier in any of them.

If a repo has uncommitted secrets

If uncommitted changes include files that may hold secrets, Relay won’t commit them even when asked. Commit or stash those yourself, then ask again.