Deploy a GitHub repo without a percher.toml
Connect a repo with no config — Percher detects the framework and generates one just for that deploy.
Connecting a GitHub repo no longer needs a committed percher.toml. If the repo doesn't have one, Percher detects the framework when it clones the repo — Next.js, SvelteKit, Astro, Vite, Express, FastAPI, Django, a static site, and more — and generates the config for that deploy. Nothing is written back to your repo, and the deploy card shows what it found.
Detection runs on every push, so it keeps up as the repo changes. Commit a percher.toml when you want to pin the config or set what detection can't infer — a custom health path, a build command, a database mode — and the committed file always wins.