GitHub connection

The GitHub connection lets CLEA move sitemap markdown files from the workspace into a repository.

This is how sitemap planning becomes a real content system. The workspace holds the files first. GitHub sync writes those files to the connected repo.

The user connects GitHub and selects a repository.

If GitHub is not connected, the sitemap can still be used for planning and drafting. It just cannot sync files to the repo yet.

The sync uses the selected repository and its default branch.

CLEA writes a commit with the sitemap expansion files. The commit message names the CLEA sitemap sync and the number of pages synced.

The GitHub integration writes under `/clea-sitemap-expansion`.

That folder is the strict place for exported sitemap pages. It helps keep CLEA page work separate from the rest of the codebase.

CLEA can work on the markdown files in the dashboard first.

When the user syncs, the current sitemap markdown files are sent to GitHub. This means review should happen before sync, not after.

Review the markdown, URL, title, description, links, and JSON-LD before syncing.

GitHub sync is not the same as final content approval. It moves files into the repo. The user still needs to trust the page content.

Common problems are simple:

• GitHub is not connected.
• No repository is selected.
• The sitemap folder is missing.
• Two sitemap files would create the same GitHub path.
• A markdown file has missing stored content.

Check whether this sitemap is ready for GitHub sync.
Look for missing URLs, duplicate paths, weak metadata, and pages that need human review.