Sync a GitHub repository
Connect a GitHub repository and refresh the collections derived from its remote branch. Link your GitHub account in Evlio first and grant access to the repository.
Requires evlio-cli 1.2.0 or later. Run evlio --version to check your installed version.
Connect and sync
evlio repo list
evlio --yes repo connect acme/payments --branch main --wait
evlio --yes repo sync acme/payments --wait
evlio repo status JOB_ID --wait
Replace acme/payments with your repository and JOB_ID with the returned scan job. A new connection uses static scanning unless you explicitly enable AI scanning with --ai. Reconnecting or syncing an existing source uses its saved settings; use repo connect to change the branch or scanning options.
Without --wait, a successful submission means the scan was accepted. Save the job ID and use repo status to check completion. --wait-timeout sets how long the CLI waits; its default is 900 seconds. A timeout or interrupted terminal does not cancel the server-side scan.
Use it in automation
evlio --yes --json repo sync acme/payments --wait --wait-timeout 600
Repository sync reads the remote branch, not uncommitted local files. Source reconciliation can reorganize or remove generated collections and associated MCP resources when routes disappear. Review the results. Syncing collections does not automatically publish changed MCP tool definitions.
Troubleshooting
If GitHub access fails, reconnect the account or grant repository access. If a job is still running after a timeout, inspect the existing job before starting another scan. Confirm its completed result and the expected collection endpoints before publishing. Connecting a new repository counts toward your plan's repository limit; at the limit, repo connect exits with code 5 and reports "Synced repos (N) limit reached for this plan". See Plans and usage limits.
On this page
- Sync a GitHub repository