evonx
Guide

How to connect an existing GitHub repository

Follow these steps in Evonx to your repository imported into Evonx with evolution threads and PR-based delivery.

Step-by-step

Prepare repository access

Ensure you can install the GitHub integration with least-privilege scopes.

Import into a business

Link the repo to the Evonx business that should own evolution work.

Document architecture

Add a short README section describing modules Evonx should respect.

Start a focused thread

Pick one feature or fix; avoid boiling the ocean in the first prompt.

Use previews

Validate changes in preview before opening or merging the pull request.

Align with CI

Keep existing tests and branch protections; treat AI output like any contributor.

Outcome

Your repository imported into Evonx with evolution threads and PR-based delivery.

FAQ

What do I need before importing a repo?

Access to the repository, a clear first change request, and agreement on branch/PR conventions with your team.

Does Evonx rewrite the whole codebase on import?

No. The workflow is scoped evolution—preview a change, review a pull request, merge when acceptance criteria pass.

How does this differ from greenfield templates?

Templates bootstrap new apps. This guide assumes production history you continue developing.

Build production software with Evonx

Start from a template or connect an existing repository. Evonx helps you ship real applications with preview, evolution threads, and pull-request delivery—not disposable demos.