What it is
ARVO keeps a version of a run’s code each time it changes. You can see what changed, when and why, compare any two versions or the code of two runs side by side, and make an earlier version the run’s code again.
Each file’s content is stored once, however many versions hold it, so ten repair rounds cost only the files they touched.
Turn it on
In ARVO Studio Setup, turn on Keep Code History in the Generation group. From then on, every run keeps its versions, and the run card shows Code History and Compare Code.
Turned off, nothing more is recorded and the two actions are hidden. The history already kept stays.
Code History
On the run card, choose Code History. It lists every version of the run’s code, newest first, each with its reason:
- generated, or regenerated;
- object ids allocated, when the compile writes the project’s version, object range and identity into app.json;
- each repair round, with how many errors in how many files;
- a repair after failing tests;
- a zip attached, or translations added;
- Copilot’s review of a pull request applied;
- brought in from GitHub;
- an earlier version restored.
From a version, choose:
| Action | What it does |
| Compare with Previous | Compares it with the version before it. |
| Compare with Another Version | Compares it with another version of the same run, which you pick. The older one is shown as Before. |
| Use This Version | Makes it the run’s code again. Every version stays in the history, and the restore is kept as a new one. The run must compile again before it is deployed or goes to GitHub. |
Compare Code
On the run card, Compare Code compares this run’s code with the code of another run of the project, which you pick. Code History opens the same page for two versions.
The top of the page says what is compared, as Before and After, and counts the files, for example 2 changed, 0 added, 0 removed – 3 with spacing changes only, 4 unchanged.
Below, each file has a line:
| Column | What it shows |
| Change | Changed, Added, Removed, Spacing only or Unchanged |
| Object | The object the file declares, for example codeunit 59990 hlm Delivery Note |
| What changed | The change in plain words, for example CountOrderLinesAndWarn added; other lines changed |
| File | The file’s place in the app |
Choose a file to see it side by side, with the lines that changed marked. Show unchanged files and files with spacing changes only and Show spacing changes decide how much you see.
For a project linked to GitHub, Compare with GitHub on the run card compares the run’s code with the app on the GitHub branch as it is now.
Good to know
- Spacing only means the file differs only in spaces or line endings. GitHub, for example, keeps files with Unix line endings.
- One setting per line. While Keep Code History or GitHub Integration is on, ARVO writes app.json with one setting per line, so a changed setting shows as one changed line.
- Runs from before. A run made before Keep Code History was turned on has no versions: Code History says so.