GitHub Integration

The GitHub integration is the native publishing path for repository-backed websites.

What it can do

After connection, ReachLLM can:

• Read the repository tree.
• Read existing files to learn the site's framework and content format.
• Write Markdown, MDX, HTML, or other source files.
• Commit image assets, such as generated article hero images, into the repository.
• Open pull requests by default.
• Commit directly when the brand is configured for direct publishing.
• Add or update blog posts, schema blocks, llms.txt, robots.txt, and safe GEO fixes.

How to connect

1. Open Account > Integrations.
2. Go to Content & CMS.
3. Click Connect on GitHub.
4. Install the ReachLLM GitHub App on the repository you want to use.
5. Choose the repository and default branch.
6. Keep Pull Request mode unless you want direct commits.

How the agent uses it

For GitHub-backed sites, the agent should inspect the repo before writing:

1. Read the repo tree.
2. Open an existing post or page to copy frontmatter and formatting conventions.
3. Write the complete file content.
4. Add image assets to the same pull request when the content needs pictures.
5. Open a pull request for review.

Generated article hero images are committed to public/images/reachllm/ by default and referenced from the article body as /images/reachllm/.... If your framework uses a different public asset folder, tell the agent the repository media directory or exact media path before uploading. For example, use media_dir: "static/uploads" for a folder or media_path: "public/assets/hero.png" for a specific file. The agent can also pass public_url when the site serves that path differently from the repository path.

For standalone image uploads, the agent uses cms_upload_media. The result includes the repository path, public URL, branch, status, and pull request URL when the upload opens a PR.

This is separate from workspace GitHub context tools. The Content & CMS GitHub connection is the publishing path.