Skip to content

Approve a change list

An AI coding assistant, such as Claude Code or Codex, works in Ronja with your sign-in. When it has built or changed something (workflows, apps, tables, automations, changes to a managed database), it does not put it live itself. It asks you, with a change list: the list of what would change, and an exact copy of the files behind it. Nothing changes in Ronja until you approve it.

The request lands in the Notifications bell at the bottom of the sidebar: A change list is waiting for your approval, with who proposed it and how many changes (“ronja-cli on adams-laptop proposed 3 changes.”). The name is that of the sign-in the assistant used, as the Access tokens tab of your Settings lists it. Click it to open the change list. It is not emailed. The assistant also gives you the link; it opens the same page.

The title reads Change list for prod (the name of the place the assistant’s files deploy to) or Change list, with its status beside it. Under the title: who proposed it, when, and a count such as “2 created, 1 modified”.

Three groups follow:

  • Created: new in Ronja. Each row gives its Kind (such as Workflow, App, Module, Table, Metric or Automation), Name, Folder (where it sits in the assistant’s files) and Goes into, the feature it will be created in.
  • Modified: already in Ronja, changed to match the files. Open shows what is live now. A database change appears here under Database changes, one migration per row, with Show SQL for the exact statement that will run.
  • Removed from the folder: a change list never deletes anything in Ronja. The group lists files the assistant removed from its folder: the folder no longer updates what they made, and it stays in Ronja. To delete it, do that in Ronja.

A last line counts the items that are already up to date and not shown. The page lists what changes, not what changed inside each file; ask the assistant if you want to see that.

  1. Read the list. Check the feature under Goes into for anything new, and the SQL of any database change.
  2. Click Approve and deploy.

The status changes to Deploying. Ronja deploys exactly the copy listed, as you, so each change goes through only if you could have made it yourself. It usually takes a few minutes, and you can leave the page.

Before it writes anything, Ronja checks the copy against Ronja as it is now. If deploying it would change something the page did not show you (say, the assistant changed the same workflow again after proposing), nothing is deployed and the page names what moved.

Only one of your change lists deploys at a time. Approving another while one is deploying is refused: approve it when the first has finished.

  1. Click Reject.
  2. Optionally, write a Reason: what should change before you would approve.
  3. Click Reject change list.

Nothing is deployed, and the status reads Rejected with your reason, which the assistant can read. It has to propose again.

Status What it means
Waiting for approval Nothing has changed yet. It waits 24 hours.
Deploying You approved it, and Ronja is deploying it.
Deployed The deploy finished. Each change shows its outcome.
Partly deployed The deploy stopped partway: some changes are live and some are not.
Failed The deploy stopped before anything listed went live, or Ronja can’t confirm what did.
Rejected You or an Admin rejected it. Nothing was deployed.
Expired Nobody approved it within 24 hours, or the assistant proposed the same folders, for the same destination, again and the newer change list replaced this one. Nothing was deployed.

After a deploy, each row has an Outcome:

Outcome What it means
Created It is new in Ronja, in the feature shown.
Updated It is live with the change.
Moved Its file was renamed in the folder, and Ronja now knows it by the new name.
Left in Ronja It was removed from the folder, and what it made is still in Ronja.
No change It already matched.
Sent for review It is in a shared feature you can’t publish to directly, so it went for review, as it would if you had made the change yourself. An Admin or a maintainer of the feature decides it.
Refused Ronja refused it. The reason is under the label.
Not deployed The deploy stopped before it got to this one.
Not confirmed Ronja can’t tell whether it went through.

A change that went live while the rest of its folder did not finish keeps its label, in yellow.

A database migration shows Applied, Already applied, Not applied, Not run, Refused, Not confirmed, or Failed. A failed migration undoes the other migrations for that database, and nothing after it is deployed.

The page says where the deploy stopped: Nothing was deployed, The deploy stopped partway (each folder that did not finish is listed with why, and each change shows its own outcome), or, when Ronja did not hear back, that it can’t confirm what landed.

Either way, ask the assistant to propose again. A failed change list can’t be approved a second time. The new one holds only what is still left, because whatever already went live now counts as up to date.

You can open any change list in the organization from its link, and Reject one that is waiting. Only the person it was proposed for can approve it. Anyone else who opens the link sees Change list not found.

While you act as someone, you can’t propose, approve or reject a change list for them: Ronja answers Not while acting as followed by their name, and a waiting change list stays waiting.