Publish articles to Bitbucket

Connect Bitbucket once and you can publish any Clevera article to a Bitbucket repository as a Markdown file, ready for a docs site or a docs/ folder next to your code. This article covers connecting, choosing the repository and folder, what the file looks like and how updates work.

Before you start#

• Plan: publishing to Bitbucket 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 Bitbucket. Everyone else who can open the article can publish once it's connected.
• Bitbucket Cloud only: Clevera connects to bitbucket.org. Bitbucket Data Center and Server aren't supported.
• Access in Bitbucket: the connecting account must be a member of the repositories you want to publish to, with write access to the main branch.
• 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 Bitbucket#

1. Open Integrations#

   In the sidebar, open the workspace menu and choose Integrations. Find Bitbucket under Available integrations (or the Development tab) and click Connect.

2. Grant access in Bitbucket#

   Sign in to Bitbucket if you aren't already. Bitbucket asks you to grant Clevera access:

   Bitbucket permission	Why
   Account: read	To show your Bitbucket name in Clevera
   Repositories: read	To list repositories and check whether a file already exists
   Repositories: write	To commit the Markdown file

   Click Grant access.

3. Check the connection#

   You return to Integrations with "Bitbucket connected successfully to" followed by your Bitbucket name. Bitbucket moves to the Connected list with a Connected badge. Before you publish anything it reads "Nothing published yet".

Publish an article#

1. Open the Publish tab#

   In the editor, click Share and open the Publish tab. Under Publish the article, Bitbucket 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 repository and folder#

   Click Publish next to Bitbucket, then choose where the article goes:

   Field	What to pick	Notes
   Repository	The Bitbucket repository for the file	Lists up to 100 repositories you're a member of, across your Bitbucket workspaces. 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 Bitbucket." and the file opens in Bitbucket in a new tab.

Where the file goes#

• Branch: the repository's main branch (usually main or master). 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 Bitbucket account that connected the integration.

Branch restrictions#

If the repository has a branch restriction on its main branch (for example, changes only through pull requests, or writes limited to certain people), Clevera's commit is refused with "Failed to create file in Bitbucket." Add the connected account to the people who can write to the branch under Repository settings → Branch restrictions, or publish to a repository without that rule.

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"
---

Bitbucket's own file view doesn't render alerts or HTML, so callouts look like plain quotes and toggles may show their tags as text. A docs site built from the repository can render them if its generator supports them.

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. Markdown files can't hold a player, so it's a link. 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 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#

If a static-site generator (such as MkDocs, Docusaurus or Hugo) builds your docs from the repository, point Folder at the folder it reads. Each publish is a normal commit, so Bitbucket Pipelines or your other build runs as usual. Most generators read title from the front matter and ignore fields they don't know.

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 in Bitbucket 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 Bitbucket." 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 in Bitbucket yourself. Nothing in Clevera deletes files from your repository.

Disconnect Bitbucket#

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

Disconnecting deletes Clevera's tokens. To revoke Clevera's access on Bitbucket too, open your Bitbucket Personal settings, go to App authorizations and revoke Clevera.

Troubleshooting#

Related#