Company blog

The company blog is another destination on the brand. Publishing writes a markdown file through the GitHub API. The product does not clone the repository, and it does not call GitHub unless the server is allowed to.

Open Settings, then Blog destination, for the current brand.

What you set

Setting	What it does
Repository	The GitHub repository that receives the post. Use owner/name.
Branch	The branch a direct commit uses. The default is main.
Posts folder	Where the markdown file goes. The default is content/blog.
Images folder	Where a hero image goes when images are stored in the repo.
Image mode	repo commits the image. link puts a media base URL in the hero field and does not upload the file.
Publish mode	pull_request (the default) opens a pull request. commit writes straight to the branch.
Front matter	Placeholders for title, date, slug, description, tags, hero, and body.

A pull request uses a branch named automagic/blog/{key} and can include the hero image. A direct commit does not overwrite a file that already belongs to a different post. The worker writes the file when the job is due. GitHub is not asked to schedule a future committer date.

In the composer, a blog version has a slug. Letters, numbers, and hyphens. The description is the caption field.

Credentials stay on the server

The connection can use a fine-grained token or a GitHub App installation token. The private key never leaves the server, and the settings screen does not show it. Connect checks that the token can see the repository.

Writes stay off until BLOG_HTTP_ALLOW_NETWORK=1 on the server that should commit. Leave the token and the private key empty in git.

If a write times out or the response cannot be read, the job is uncertain. Lookup reads the pull request or the commit. It does not create another one.

Analytics does not read the blog. The blog is a file in a repository, not a social network metric.