GITHUB INTEGRATION
GitHub integration
GitHub brings analysis into the repository when content lives in files or needs technical review before deployment.
Connect a repository
Select the correct project and connect GitHub with the minimum scope needed. Confirm repository, branch and path before reading or preparing a file.
The integration preserves review: proposals should go through your normal pull request, checks and approval workflow.
Read and prepare content
Use GitHub Content to locate the file behind a URL or editorial piece. Review front matter, links, components, images and build rules before editing.
When AI creates content, keep the reason for the proposal and compare the diff with the original.
Before merging
Check that the change does not break routes, imports, variables, Schema or internal links. Run the repository build and tests.
A person with the right permissions and deployment knowledge should merge the change. Serplenty prepares context; it does not replace repository controls.
Common errors
A repository that is not visible usually indicates insufficient authorization or the wrong project. A file that does not load may depend on branch, path or token permissions.
If the site is generated from another source, confirm the canonical source before applying a change.
Use a branch or pull request whenever content will reach production.