All integrations
Live · GitHub App / pull requests. Prepares blog content as pull requests. Merge and deployment are separate steps. Automatic merging needs an explicitly configured, authorized workflow.
GitHub
Capabilities and access
Documentation reviewed on 22 October 2026. This is a documentation check, not a test in your connected account. Capabilities, required permissions and plan availability can evolve. Confirm details marked unverified before relying on them.
Current support
Live · GitHub App / pull requests
Read access and data
Selected repository and blog folder; exact file-read permissions require confirmation.
Drafting, publishing and updates
Prepares blog content as pull requests. Merge and deployment are separate steps. Automatic merging needs an explicitly configured, authorized workflow.
Permissions and prerequisites
Install the Citera GitHub App and grant the intended repository access. Choose the repository per brand. Organization approval, exact App permissions and protected-branch requirements must be confirmed for your account.
Plan availability
Repository publishing entitlement: requires confirmation.
Limitations
A builder name alone does not establish compatibility: the site needs a suitable GitHub repository. A pull request is not a live deployment. Universal code edits, rollback and automatic merges are not established by the setup article.
How it works
Start the connection
Choose GitHub in Settings → Integrations for the intended brand.
Configure the destination
Install the App, select the repository and identify the blog folder; use discovery if needed.
Verify the connection
Check that the repository is selected. Review the first content pull request, then follow your merge/deployment checks before confirming the public URL.
Confirm current support
Capabilities, permissions and plan availability can evolve. Check your current integration screen and the documented limitations above before enabling automation.
Frequently asked questions
Answers about setup, permissions, automation and availability.
What can this connection read and change?
Selected repository and blog folder; exact file-read permissions require confirmation. Prepares blog content as pull requests. Merge and deployment are separate steps. Automatic merging needs an explicitly configured, authorized workflow.
Which plan includes it?
Repository publishing entitlement: requires confirmation.
What are the limitations?
A builder name alone does not establish compatibility: the site needs a suitable GitHub repository. A pull request is not a live deployment. Universal code edits, rollback and automatic merges are not established by the setup article.
Which permissions and approvals are required?
Install the Citera GitHub App and grant the intended repository access. Choose the repository per brand. Organization approval, exact App permissions and protected-branch requirements must be confirmed for your account. Use draft-only or approval-required settings for review. Enable autonomous publishing only for the destinations and content types you intend to authorize.
