Publish articles to GitHub

Connect GitHub once and you can publish any Clevera article to a repository as a Markdown file, ready for a docs site, a wiki-style docs/ folder or a README collection. This article covers connecting, choosing the repository and folder, what the file looks like and how updates work.

Before you start#

• Plan: publishing to GitHub is part of the Pro and Custom plans. On Free and Starter the Publish tab shows "Publishing to your tools is included in Pro". See Choose a plan.
• Role in Clevera: only the workspace owner or an Administrator can connect or disconnect GitHub. Everyone else who can open the article can publish once it's connected.
• Access in GitHub: the person who connects needs write access to the repositories you want to publish to, and the right to install a GitHub App on that personal account or organization (or an organization owner to approve it).
• An article: you publish the article that belongs to a video or recording. Generate it first; see Turn a recording into an article.

Publishing uses no credits.

Connect GitHub#

1. Open Integrations#

   In the sidebar, open the workspace menu and choose Integrations. Find GitHub under Available integrations (or the Development tab) and click Connect. The button appears when you point at the card.

   

2. Authorize Clevera on GitHub#

   GitHub asks you to authorize the Clevera AI app. It requests read access to your organization memberships, so Clevera can list the accounts you belong to. Click Authorize.

3. Install the app on your repositories#

   GitHub then opens the Clevera AI app installation page. Pick your personal account or an organization, then choose All repositories or Only select repositories. The app asks for:

   GitHub permission	Why
   Contents: read and write	To create and update the Markdown file
   Metadata: read-only	Required by GitHub for every app; lets Clevera list repositories

   Click Install. Repeat for each organization you want to publish to.

4. Check the connection#

   Back on Integrations, GitHub moves to the Connected list with your GitHub account or organization name and a Connected badge. Before you publish anything it reads "Nothing published yet".

   

Add or remove repositories later#

Clevera only sees repositories the app is installed on. To change that, open Integrations, click GitHub, and under Access click Repository access. On GitHub, open the account, click Configure and change the repository list. New repositories show up the next time you open the Publish tab.

Publish an article#

1. Open the Publish tab#

   In the editor, click Share and open the Publish tab. Under Publish the article, GitHub shows Connected and a Publish button.

   The article is published in the language you have open in the editor. Switch language in the top bar first to publish a translation.

2. Choose the account and repository#

   Click Publish next to GitHub. Then choose where the article goes:

   Field	What to pick	Notes
   Account	Your personal account or an organization	Only shown when your repositories belong to more than one account
   Repository	The repository for the file	Lists up to 100 repositories, most recently updated first. The first one is selected for you
   Folder	A path such as docs or articles/guides	Starts as docs. Leave it empty for the repository root. Folders that don't exist yet are created

   

3. Publish#

   Click Publish. You see "Checking for an existing article…", then "Publishing…". When it's done you see "Published to GitHub." and the file opens on GitHub in a new tab.

Where the file goes#

• Branch: the repository's default branch (usually main). Clevera commits straight to it; it doesn't open a pull request and you can't pick another branch.
• File name: the title in lowercase, with spaces turned into hyphens, ending in .md. "Create your first invoice" becomes create-your-first-invoice.md.
• Commit message: Add article: <title>, or Update article: <title> when you replace an existing file.
• Commit author: the GitHub account that connected the integration.

What the file looks like#

Clevera writes GitHub-flavored Markdown with a short front matter block at the top:

---
title: "Create your first invoice"
created_at: "2026-10-12T09:30:00+00:00"
updated_at: "2026-10-12T10:05:00+00:00"
source: "Clevera"
---

If the video's share link is on, the file starts with a quoted line, Watch the video tutorial, that links to the video player. GitHub doesn't play embedded videos in Markdown, so it's a link rather than a player. If the share link is off, there's no video line, and turning the link off later makes an existing one stop working.

Images#

Screenshots aren't copied into your repository. Each image in the file links to the file on Clevera's servers through a signed address that works for one year from when you publish. To keep images working, publish the article again (choose Replace the existing article) within the year; each publish renews the links.

Anyone who has the image address can open the image, even if the repository is private.

Use it with a docs site#

Most static-site generators that build from a repository (such as Docusaurus, MkDocs, Jekyll or Hugo) read title from the front matter and ignore fields they don't know. A common setup:

1. Point the Folder at the folder your docs site reads, for example docs or content/guides.
2. Publish each article there; your site's normal build picks up the new commit.
3. Check whether your generator renders GitHub alerts and <details>; some show alerts as plain quotes.

Update an article you already published#

Publishing only goes one way. Edits you make in Clevera stay in Clevera until you publish again, and changes made to the file on GitHub never come back to Clevera.

When you publish to the same repository and folder, Clevera finds the file with the same name and asks what to do: "An article with this title already exists in GitHub." Click View it to open the existing file, then choose:

If the title changed in Clevera, the file name changes too, so publishing creates a new file next to the old one. Delete or rename the old file on GitHub yourself.

Nothing in Clevera deletes files from your repository.

Disconnect GitHub#

1. Open Integrations, click the ⋯ menu on the GitHub row and choose Disconnect (or click GitHub and then Disconnect).
2. Confirm. "You can no longer publish to it from the editor. Content you already published stays in GitHub."

Disconnecting deletes Clevera's access token. To remove Clevera's access on GitHub too, uninstall the Clevera AI app (GitHub Settings → Applications → Installed GitHub Apps → Configure → Uninstall) and revoke the authorization under Authorized GitHub Apps.

Troubleshooting#

Related#