Fix GitHub connection issues

Acrosite publishes by committing to your GitHub repository through the Acrosite GitHub App. When that connection is not working, publishing cannot commit. This guide walks the common causes.

Who this is for

Workspace Owners, Admins, and Developers who manage GitHub Setup.

Check the connection

1. Open the project and go to GitHub Setup.
2. Confirm the status reads Connected and that a Repository and Target Branch are selected.
3. If it does not, re-run Connect GitHub and finish the install. See Connect GitHub.

Common causes

• The repository is not in the list. The GitHub App was not granted access to it. Open your GitHub installation settings, add the repository, then refresh the list in Acrosite. See Choose a repository and branch.
• The App is not installed. Re-run Connect GitHub and complete the install on the repository's owner account.
• The repository was renamed, moved, or deleted. Reconnect to the current repository.
• The target branch is protected. Protected branches can block direct commits. Point Acrosite at a branch it can write to, or adjust the branch protection rules.

Never paste a token

If commits still fail

Open Publish Logs and find the failed job. If it failed at the GitHub commit stage, the cause is usually one of the above. For the full publish-failure checklist, see Troubleshoot publishing failures.

Next steps

• Connect GitHub
• Choose a repository and branch
• Troubleshoot publishing failures