What it is
Developers keep working on the app in GitHub: they fix a label, add a codeunit, change a layout. ARVO notices what they changed since it last looked, tells you, and lets you bring it all into ARVO Studio. The next generation then builds on their work instead of writing over it.
Turn it on
In ARVO Studio Setup, turn on Bring In GitHub Changes in the GitHub group. It needs GitHub Integration and a project linked to a repository (see Connect ARVO Studio to GitHub).
Turned off, ARVO never looks for developers’ changes, and generates and opens pull requests exactly as before.
See what developers changed
When the project card opens, ARVO compares the app’s folder at the last commit it saw with the branch as it is now. This happens for a signed-in developer, and only while no background job is working on the project. When developers changed files:
- a notice says Developers changed 3 file(s) of the app in GitHub that ARVO Studio has not brought in yet, with Review;
- Changes in GitHub on the GitHub tab shows the number in red.
Choose Review, the number, or Check GitHub for Changes to open Repository Changes. Its top shows the repository, the branch and folder, the two commits compared, and a summary. Each file then has a line:
| Column | What it shows |
| Path | The file, from the repository’s top folder |
| Change | Added, Changed or Removed |
| Who changed it | The developer’s GitHub login, or the name in the commit |
| Commits | In how many of the developers’ commits the file changed |
| Last Commit | The newest of those commits, with its message and when it was made |
Open in GitHub opens the file as it is now, and Check Again reads the branch again. When nothing changed, a message says No changes outside ARVO Studio, with the commits compared.
Bring In All Changes
On Repository Changes, choose Bring In All Changes. It brings in every change in the list at once, whichever line is selected. One file can’t be brought in alone: ARVO’s next pull request starts from the commit brought in, so a change left out would be undone.
ARVO asks first, then makes a new run from the app’s code on GitHub, at exactly the commit the list was read at:
- the run’s GitHub tab shows Code From From GitHub, Starts From Commit, and Commit with who made it and its message;
- it compiles at once, as it is, with no AI: there is no AI-spend question and no AI repair;
- when it doesn’t compile, the run says so in plain words. Fix the code in GitHub, or choose Generate Source to build on it.
A run brought in from GitHub keeps the developers’ code exactly as it came, so Regenerate Source into it is refused. Choose Generate Source on the project card instead: the new run builds on this code.
Before ARVO generates or opens a pull request
When developers have changed files that ARVO hasn’t brought in, ARVO asks before Generate Source, the chains that generate, Regenerate Source, Create Pull Request and Update Pull Request. The choices are, for example:
- Bring them in and generate: ARVO makes the run from GitHub’s code first, and the generation starts from it.
- Generate without them: the generation goes ahead without them. When its pull request is merged, GitHub keeps the developers’ changes, and shows a conflict where both changed the same lines.
- Cancel.
A new generation always starts from the newest code ARVO knows is right. That’s the newest of three runs: the run brought in from GitHub, the run whose pull request was merged most recently, and the version installed. The trail says which, for example upgrade mode: 8 file(s) of run 777 – its pull request #8 is merged into main. The run records the commit it started from, and its pull request starts from that commit.
Compare with GitHub, and what never counts
Compare with GitHub on the run card compares the run’s code with the app on the GitHub branch as it is now, file by file and side by side (see Code History and Compare Code).
ARVO never counts these as developers’ changes:
- ARVO’s own pull requests: a file whose content ARVO delivered, and a file ARVO’s newest pull request removed;
- the standards file ARVO writes for Copilot;
- the compiler’s dependency apps;
- rule files for AI tools, such as AGENTS.md in the app’s folder. ARVO handles those as GitHub Repository Coding Rules.
A file ARVO delivered that a developer then edited does count, as Changed.