GitHub

Appentic integrates with GitHub via a first-party GitHub App. Once it's installed on your account or organisation, Appentic can read repository metadata, receive push webhooks, and authenticate to clone your code at build time. In practice that means your existing git workflow is the deploy workflow: push to main, watch the build in the dashboard, done.

Installing the app

From Settings → Integrations → GitHub, click Install. GitHub will prompt you to choose which account or organisation to install the app on, and which repositories to grant access to. You can grant access to:

• All current and future repositories. Convenient if you own the organisation and plan to deploy several services from it.
• A specific subset. Safer if you only want Appentic to touch certain repos. You can change the list later from GitHub's own Integrations settings without reinstalling.

The Appentic GitHub App only reads metadata and listens for push webhooks on repositories it has access to. It does not read any repository you haven't explicitly granted.

Deploying on every push

Each service you create is linked to a specific branch (typically main). When Appentic receives a push webhook for that branch, it:

1. Clones the repo at the pushed commit.
2. Runs your build command, using cached layers where possible so repeat builds are fast.
3. Starts the new revision and runs its health check.
4. Swaps traffic over if the new revision is healthy, or marks the deploy failed and keeps serving the previous revision otherwise.

There's no separate CI system to configure, no deploy script to maintain, and no secret to plumb into GitHub Actions. The branch is the source of truth, and the build happens on Appentic's builders.

PR previews

Per-PR preview environments are on the roadmap. In the meantime, the usual workaround is to create a second service pointed at a long-lived preview branch (say, preview) and merge feature branches into it when you want to share a test link with a teammate or a designer.

Revoking access

If you want to disconnect Appentic from GitHub entirely, uninstall the Appentic GitHub App from your GitHub settings. Running services keep running, they just won't receive any new deploys until you reconnect. This is the same mechanism a departing employee would use to revoke their own access.