Can my site update when I push to GitHub?

Yes, from the Starter plan, for a repository you can push to. On Home, Import from GitHub puts a website from one of your repositories online, and each push to its branch then updates the site after the same checks as an upload. A website's own files go up as they are; a project with a build script (Vite, React, Astro and the like) is built on your own GitHub first. A Next.js app is built as a website by itself (a static export, without changing your next.config), unless it has parts that run on a server (middleware, API routes, server actions): those can't become a website of files, so Furge says so before building and offers to host it on Vercel instead. If the project reads settings while it builds (a Supabase address and key, say), Import from GitHub asks for them first: see Keys & variables. A push that doesn't pass changes nothing on the live site: the site's GitHub settings say why in plain words, first, with the lines where it went wrong, a button for the fix (add the settings it needs, Build again, Host it on Vercel) and its run on GitHub, and Furge emails you. Each deploy shows its commit and how far it's got, and Roll back to this puts an earlier version back at once; pushes then wait until you switch publishing each push back on. A design you pushed from Furge can switch to updating from GitHub too: press Update from GitHub after Push to GitHub.

Steps

  1. On Home, press Import from GitHub (connect GitHub first if Furge asks).
  2. Choose the repository, check the branch and folder Furge found, and press Publish from GitHub.
  3. Open the site's card on Projects to see each deploy, roll back, turn off publishing each push, deploy by hand, or stop updating from GitHub.

Also asked as

Related

Still stuck? Ask Furge Help, the round chat button at the bottom right, or contact the Furge team.

← All of Furge's docs