Oat commits the revision you approved to your repository.

If your site builds from a repository, Oat commits approved revisions as Markdown and follows the deployment.

GitHubPublishNeeds the Oat GitHub App on one repository.

An approved revision becomes a Markdown file committed with a message naming it, so repository history is an approval record.

Oat reads and writes only what is listed here.

Oat reads.

  • The branch and folder you chose
  • Deployment status, when the host reports it

Oat writes.

  • One commit per approved revision

The permission is narrow and yours to revoke.

Contents access to one repository, so Oat sees no other.

Connecting takes three steps.

  1. Install the Oat app on your repository.
  2. Pick the branch and folder Oat writes to.
  3. Add the Vercel hook if pushes skip deploys.

The decision stays yours.

A commit needs a revision approved for this destination, and Live confirmed waits until the page answers.

Creators ask this first.

What if the deploy fails?
The piece shows the failed deployment and its error, short of Live confirmed.

Bring your accounts with you.

Create your account

Connect it while you set up, or read about LinkedIn next.