See your site's build status

After Acrosite commits a publish, your host builds your site. Build status shows what was reported to GitHub about that commit — by your hosting provider, or by other checks that run on your repository — so you can see whether the build finished without leaving Acrosite.

Who sees it and where

Workspace Owners and Admins, who also see Publish Logs. Build status appears:

• in a content item's Published File panel, as Site Build;
• on the project's Publishing page, under each publish job's deployment;
• in the workspace Publish Logs, on each publish job.

Deployment Logs keep recording only the deployment trigger and its response.

Build status covers only commits Acrosite made. An item you imported from your repository shows none until you publish it from Acrosite.

What each status means

• Deployed — your hosting provider reported this commit as deployed.
• Build Failed — your hosting provider reported a failed build.
• Building — your hosting provider reported that it is building this commit.
• Build Cancelled — your hosting provider cancelled the build, often because a newer commit replaced it.
• Checks Passed — the checks reported to GitHub passed, but none was recognized as your hosting provider's build. This does not confirm a deployment.
• Check Failed — a check reported to GitHub failed, such as a test. It was not recognized as your hosting provider's build.
• Checks Running — checks reported to GitHub are still running.
• No Build Status — nothing was reported to GitHub for this commit. Check your host.
• Build Status Unavailable — Acrosite could not check GitHub; the reason is shown with what to do.

Acrosite recognizes a host's build only once it has seen that host's own deployment status. Some hosts do not report a production deploy to GitHub at all, and some are not recognized yet; for sites on those hosts you see Checks Passed, Check Failed or No Build Status rather than Deployed.

How Acrosite checks

Acrosite asks GitHub when an Owner or Admin opens a page that shows the publish: every few seconds while a recent build is running, less often later, and not at all once the commit is a day old. It never changes anything in your repository or on your host to do so, and it does not check while a workspace is suspended or while the repository connection needs attention.

If build status is unavailable

• Accept the updated permissions: the Acrosite GitHub App asks for read-only Checks and Commit statuses access. An owner of the GitHub account accepts it in GitHub's settings for installed apps; build status then appears on its own.
• Repository access: if Acrosite can no longer reach the repository, reconnect it in GitHub Setup — see Connect GitHub.
• Request limit: GitHub limits how often it can be asked; Acrosite checks again shortly.
• GitHub could not be checked: GitHub refused or did not answer this time, for example because of an IP allow list on your GitHub organization. Acrosite keeps the last answer it received and checks again shortly.