Skip to main content
GitHub, GitLab, and Bitbucket are repository Publishing Connections. They save generated drafts as Markdown for teams that publish through a static site or another repository workflow. Saving a file does not itself deploy your site.

​
Connect a repository

  1. Open the Project’s Settings → Integrations and choose the repository provider under Code repositories.
  2. Authorize the account shown in the provider panel. For GitHub, complete the GitHub App installation and choose an accessible repository. For GitLab or Bitbucket, finish the authorization step and choose the intended project or repository.
  3. Set the destination. Confirm the repository and branch; set a content path if your site expects Markdown in a particular folder. GitLab also offers an optional index path and host.
  4. Save the Connection and confirm the card shows the intended repository.

​
Check the output

Review the Article before sending it, then inspect the resulting Markdown file in the repository. Check its path, branch, frontmatter or content format, links, and commit history. Follow your normal review and deployment process to make the content public. Use a test Article in a nonproduction branch or repository when first configuring a destination. If authorization succeeds but no repository can be chosen, check that the account or installed app has access to it. If files land in the wrong place, update the branch or content path in the Videntic panel. If the card shows a disconnected state, reauthorize the provider before sending more drafts.
Last modified on September 28, 2026