---
title: "GitHub integration"
description: "Connect one or more GitHub accounts, sync repositories, and publish changes as pull requests."
url: https://evonx.ai/docs/integrations/github
locale: en
updated: 2026-09-04
---

# GitHub integration

Connect one or more GitHub accounts, sync repositories, and publish changes as pull requests.

GitHub stays the source of truth for imported projects. Evonx connects your
account, clones and syncs repositories into a business, and ships AI work back
as pull requests on GitHub so your existing review flow keeps working.

## Connect and import

1. Sign in to Evonx and connect GitHub (OAuth). You can attach more than one
   GitHub account and set a **primary** for new imports.

2. Pick repositories to import — one or several. Each becomes a project in the
   business. Import does not move the repo; it links it.

3. Let the codebase scan finish. The system graph is what later
   [Evolution Threads](/docs/evolve/evolution-threads) plan against.

4. Sync when GitHub has moved on without Evonx. Start previews and threads from
   the branch you mean — a stale clone is the usual reason a preview "ignores"
   a commit you know is on GitHub.

Finished threads open **pull requests** on the GitHub repository. Merge there or
from Evonx; revoke if you do not want the change. Details:
[Publishing changes](/docs/evolve/publishing-changes).

> **Note**
> Greenfield apps Evonx scaffolds also live in real git remotes. Connecting GitHub
> is how you take that code into your own org, not only how you bring old code in.

## Related

- [Import from GitHub](/docs/build/import-from-github) — the product path this
  integration enables.
- [Modernize an existing codebase](/docs/use-cases/modernize-existing-code) —
  the same loop as a worked example.