Help
How builds run
The top bar “Got the data / building from the data repo and pushing to the site repo” means this change is already in the private data repo. GitHub Actions is compiling and pushing to the public site repo — it is not stuck in the browser. You can close the tab and write the next post.
Can I leave?
Yes. After a successful save, the files are already in the private data repo. The cloud workflow compiles on its own, then pushes to the public site repo. The progress line in the admin is only this page asking GitHub how far it got. Closing the page does not stop the build.
What if I save again?
It will not queue behind the last run, and two machines will not compile the same site at once. A new push cancels the in-flight run and keeps only the latest. Saving several times in a row is usually fine; the middle runs show up under “Recent builds” on the dashboard as “Cancelled.”
How long?
Most sites take 60–120 seconds. The first build or a theme switch can take longer. The dashboard shows recent runs; you can also tap “View on GitHub” in the status bar.
Saving a draft also triggers a build, but that post never appears on the public site. See Scratch, drafts, and published.