What it is
Connect ARVO Studio to your company’s GitHub organisation, and ARVO can deliver each run’s code as a pull request, keep track of what developers change in GitHub, and follow the rule files they keep there.
Each project is one app, kept in one folder of one repository. Several projects can share a repository, each in a folder of its own. ARVO calls GitHub straight from Business Central, as the developer who is signed in.
Before you start
- A GitHub organisation that holds the repositories, or will.
- A way for developers to sign in:
- through your organisation (recommended): an owner of the organisation registers its own GitHub app once, or
- with personal tokens: each developer makes a fine-grained token on GitHub.
- Each repository needs at least one commit: ARVO refuses an empty one, because pull requests need a branch to start from.
- ARVO can ask Copilot to review its pull requests on any plan, using the signed-in developer’s own Copilot. GitHub’s automatic review rule for private repositories needs a paid plan, and the setup guide warns you when the organisation doesn’t have one.
The GitHub Setup Guide
Open Connect ARVO Studio to GitHub in Assisted Setup, or choose GitHub > GitHub Setup Guide on ARVO Studio Setup.
- Enter your GitHub Organisation as it appears in its address, for example contoso-dev in github.com/contoso-dev.
- Choose how developers sign in: Through Your Organisation, With Personal Tokens, or both.
- Register Your Organisation (an owner does this once). Open GitHub opens a pre-filled registration page:
- it asks for Contents and Pull requests, read and write, and Metadata, read;
- tick Enable Device Flow, and create no client secret and no private key;
- install the app on the repositories ARVO may use;
- paste the app’s GitHub App Client ID. It is a public identifier, not a secret.
- Personal Tokens: the guide shows each developer which fine-grained token to make: the organisation as owner, only the repositories ARVO may use, Contents and Pull requests read and write. The organisation may have to approve it.
- Sign In and Test: sign in as yourself and see what ARVO can reach.
- Finish turns on GitHub Integration.
The other switches in the GitHub group of ARVO Studio Setup each turn on one feature:
| Switch | What it turns on |
| Ask Copilot to Review | Copilot reviews every pull request ARVO opens. See Pull Requests and Copilot Review. |
| Apply Copilot’s Review Automatically | As soon as Copilot’s review arrives, ARVO fixes what it agrees with, compiles, adds one commit and answers every comment. Each round costs AI tokens. |
| Bring In GitHub Changes | ARVO counts developers’ changes and builds on them. See Bring In Developers’ Changes from GitHub. |
| Use GitHub Repository Coding Rules | ARVO follows the developers’ rule files. See GitHub Repository Coding Rules. |
Your own GitHub sign-in
Every developer signs in as themselves, from Your GitHub Sign-in on the project card’s GitHub tab. Your sign-in is kept for your user only and is never shown.
- Sign In with the Organisation. ARVO shows a code. Choose Open GitHub, enter the code and approve. The page notices the approval by itself. The sign-in then renews by itself: you sign in again only after about six months, or when your organisation withdraws the app.
- Use a Personal Token. Paste a fine-grained personal token and choose Save Token. ARVO checks it with GitHub and warns you a week before it runs out.
Sign Out of GitHub removes your sign-in from ARVO Studio. A personal token stays valid on GitHub until it runs out or you delete it there.
Link a project to a repository
On the project card’s GitHub tab:
- GitHub Repository: choose the field to pick from the repositories your sign-in reaches. The list shows each one’s visibility and default branch.
- GitHub Branch is set to the repository’s default branch. ARVO’s next pull request starts from the commit this branch is at.
- Repository Folder is set for you:
- where the repository already keeps this app’s app.json;
- otherwise the folder you typed before choosing the repository;
- otherwise app, or, when app already holds another app or another project is linked to it, the project number and the app’s name, for example 120-github.
ARVO never puts an app in a folder that holds another app. Last Seen Commit and Last Checked At show what ARVO last read on the branch, and when.
Good to know
- Public repositories. Anyone on the internet can read the code ARVO puts in a public repository. ARVO links one only after you confirm, and Repository Is Public stays visible on the card.
- Switching off. With GitHub Integration off, the GitHub tabs are hidden and ARVO makes no call to GitHub.