slew docs/deploy/push-to-deploy

Git push-to-deploy

Connect a GitHub repository to a project and slew builds and deploys it for you: push to your branch and the release goes live; open a pull request and the PR gets an expiring preview URL in a comment.

git push
  → webhook → build queued
  → source fetched at your commit
  → install + build in an isolated container
  → output deployed, CDN purged
  → live at https://<project>.slew.cloud

Connect a repository

Console: sign in at app.slew.cloud, open the GitHub page (or a project's Git section), and install the slew GitHub App on the account or organization that owns the repo — you choose which repositories it can see. The console notices the installation by itself (the installer's GitHub identity links it to your slew account); if it ever doesn't, Re-check with GitHub reconciles. Then pick the repository and branch and confirm the build recipe:

Setting	Default	Meaning
Install	`npm ci`	Dependency install command
Build	`npm run build`	Build command
Output directory	`dist`	The static output that gets deployed
PR previews	on	Preview URL per pull request

CLI: the same flow is one command — it opens the install page if needed, waits, and connects:

slew git connect owner/repo --build-cmd "npm run build" --output dist
slew git                 # connected repo + recent builds
slew git build           # rebuild the branch head now
slew git log             # print the latest build's log
slew git log <build-id>  # print a specific build's log

Every push to the branch then deploys automatically. Deploy now in the console (or slew git build) rebuilds on demand, and builds — with their logs — are listed on the project page.

When a build fails, read why from the terminal: slew git log prints the latest build's log (the header goes to stderr, so slew git log > build.log captures just the log). In the console, click a build's push/PR button to expand its log inline.

Pull request previews

With previews enabled, every opened or updated PR is built and published as a temporary share that expires after 7 days, and the build bot comments the URL on the PR. Previews update on every push to the PR.

How builds run

Source is fetched as a tarball at the exact commit via the GitHub App — no deploy keys to manage, private repos included.
The build runs in a throwaway container with no privileges: 2 CPUs, 2 GB memory, a 10-minute limit, and all capabilities dropped.
Only the output directory is deployed; the deployment records the commit SHA it was built from.
A failed build changes nothing: the previous deployment stays live.

The CLI keeps working exactly as before — slew deploy and git push-to- deploy coexist on the same project.