What it is
Once a run has compiled, ARVO can deliver its app to the project’s GitHub repository as a pull request. People review it and merge it in GitHub: ARVO never merges.
GitHub Copilot can review the pull request, and ARVO can work through Copilot’s comments for you, or turn them into feedback for the next generation.
Create a pull request
On the run card, choose GitHub > Create Pull Request. It is there for a main-app run that compiled or was deployed, never for a test app.
ARVO writes the run’s app to a new branch, arvo/<project>/run-<run>, in one commit, and opens a pull request into the project’s branch. The commit shows as Verified on GitHub. What goes in:
- the app’s files, in the project’s folder, app.json included;
- ARVO’s standards file for Copilot, .github/instructions/arvo-standards-<folder>.instructions.md. It holds the ARVO Studio coding standards as they apply to this app, so Copilot reviews against the same rules ARVO followed;
- deletions only of files that ARVO itself delivered before. A file a developer added is never removed.
The branch starts from the commit ARVO’s code started from, so GitHub keeps what developers changed since.
The description names the run and the project, what changed, the feedback notes the run carried, the coding standards in effect, and the GitHub repository coding rules. It ends with a link back to the run in Business Central.
Copilot’s review
With Ask Copilot to Review on in ARVO Studio Setup, ARVO asks Copilot to review every pull request it opens, and again after an update that changed something. It asks in the name of the signed-in developer, using that developer’s Copilot.
The run card’s GitHub tab follows the review: Copilot Review goes from Requested to Reviewing to Reviewed, with the number of comments and Copilot’s headline, for example Approved. When nothing happens within about 10 minutes, it says so. Pull Request Conversation, under the GitHub tab, shows the reviews, the comments on the code with their replies, and the general comments, as on GitHub.
Then choose what happens to Copilot’s open comments:
| Action | What ARVO does |
| Apply Copilot’s Review | In the background, ARVO’s AI fixes what it agrees with and declines the rest with a reason. ARVO compiles, adds one commit to the pull request, and answers every comment on GitHub. Costs AI tokens. |
| Add Copilot’s Comments to Feedback | Turns every open comment into feedback for the next generation, and answers each one on GitHub. To do it for one comment, choose Add to next-generation feedback under it in the conversation. |
With Apply Copilot’s Review Automatically on, ARVO applies the review by itself as soon as it arrives: one round per pull request or update. When the fixed code doesn’t compile, nothing changes and the comments stay open.
Update and merge
Update Pull Request. After a run is regenerated with Regenerate Source, from its Feedback for Next Generation page, choose Update Pull Request. ARVO adds one commit with the new code to the same pull request while it is open. An update that changes nothing adds no commit. If someone else has pushed to ARVO’s branch, ARVO stops and says so.
Merge in GitHub. Merging is the human approval step that the review exists for, so it stays in GitHub. Any merge style works, a merge commit, squash or rebase: ARVO recognises its own files by their content. After the merge, opening the run card or choosing Refresh GitHub Status shows Merged.
The run’s GitHub tab
| Field | What it shows |
| Pull Request No., Pull Request Address | The pull request, and its link on GitHub |
| Pull Request State | Open, Merged, Closed or Has Conflicts |
| Pull Request Branch | ARVO’s branch for this run |
| Base Commit, Head Commit | Where the branch started, and its latest commit |
| Copilot Review, Copilot Comments, Copilot Headline, Copilot Checked At | What Copilot’s review did, and when ARVO last looked |
| Delivered Files | How many files the pull request put in the repository. Choose it to see each file with GitHub’s fingerprint of its content. |
The fingerprints let ARVO recognise its own work later, so it never mistakes it for a developer’s change. Open in GitHub opens the pull request, and Refresh GitHub Status reads its state again.
Good to know
- In your name. ARVO opens pull requests and asks for Copilot’s review as the developer who is signed in.
- Two open pull requests. When you create a pull request while another one of the project is still open, ARVO warns you that the one merged second will conflict.
- Comments on the standards file. Copilot sometimes comments on ARVO’s standards file rather than the app. ARVO declines those without asking the AI: the file comes from the ARVO Studio coding standards, so change them in ARVO Studio.