Keep your app's code in your own GitHub repo
Your vibe's code can live in a GitHub repo you own. A teammate opens a pull request, your checks run on it, and when you merge, the app on vibes.diy updates by itself. The whole recipe is on Works with GitHub.

Three steps to set it up
Pull your app into a new repo, at its root:
shnpx vibes-diy pull <handle>/<app> --published --dir .
Add two files: .vibes/vibe.json, which names the app as <handle>/<app>,
and .github/workflows/deploy-vibe.yml, which you copy whole from the
docs page. Then add a
repository secret called VIBES_DEVICE_ID. Commit, push, and the Deploy
vibe run in the Actions tab prints your app's live URL.
Get posts like this in your inbox
One email field. Real updates. No algorithm required.
What the workflow does
Every push and every pull request runs a checks job. A push to the default
branch runs one more job, which waits for checks to pass and then runs
npx vibes-diy push, the same command you'd type at your own terminal. Pull
requests only run the checks, so a reviewer sees red or green before anything
reaches the app.
Your tests go in the checks job as ordinary workflow steps: a linter, unit
tests, a build. The deploy waits for all of them.
The secret is your account
VIBES_DEVICE_ID is a device certificate, the credential vibes-diy login
gives your own machine. It signs in as your whole Vibes account, so it belongs
in GitHub's secret store, on repos whose writers you'd trust with that
account. You make it with npx vibes-diy login, find the file with
npx vibes-diy doctor, and pipe it into GitHub with one gh secret set
command. The
deploy secret section has the
commands, including where to keep it on a team repo.
The chat and the repo together
A merge becomes the app's newest version, and the Vibes chat builds its next change on that code. A change you make in the chat comes into the repo the same way your app did on day one:
shnpx vibes-diy pull <handle>/<app> --published --dir .