GitHub handoff

Source code should land in a repo the customer owns

This flow turns a generated app package into a clean repository that can be deployed, reviewed, supported, and downloaded anytime.
Loading GitHub readiness...

Export workflow

No secrets in repo
1Customer

Create customer-owned repository

The customer owns the GitHub organization or personal account. CodeTech can guide repo creation after the customer signs in.

2AI agent

Prepare clean source package

Generate source code, README, env example, Supabase schema, quality report, deployment guide, and generation manifest.

3AI agent

Commit source code

Create an initial commit with no secrets, no local build artifacts, and a clear project handoff message.

4CodeTech

Configure protected main branch

Require build/typecheck status before merging when the project is on a managed support plan.

5AI agent

Connect deployment target

Connect the repository to Vercel or the selected host, then add environment variables from the setup concierge.

6CodeTech

Hand over access and docs

Confirm repo owner, deployment URL, env checklist, known limits, and next support path before marking the project published.

Repository package

These are the files the generated app should include before any repo push or deployment handoff.

README.md
.gitignore
package.json
app/
components/
lib/
supabase/schema.sql
docs/BLUEPRINT.json
docs/GENERATION_MANIFEST.json
docs/GITHUB_EXPORT.md
docs/DEPLOYMENT.md
docs/QUALITY_REPORT.md
.env.example

Access rule

The AI agent may prepare commits, docs, and deployment settings, but the customer authorizes account access, private credentials, billing, and ownership transfer.