Git Insights for Confluence

Please connect cloud accounts only. On-premises instances are not supported.

Let’s get in touch!

Need help?

Want to give us Feedback?

Request a new feature?

Contact us via Servicedesk or via app-support@smateso.com

Step 1: Connect Platforms

Add Macro

  • go to the chosen confluence page and type /gitinsights

  • click the correct macro

If you don’t know how to create Access Tokens have a look here.

Add token

  • Choose the provider (e.g., GitLab, GitHub, Bitbucket, Azure).

  • Enter the username (for Bitbucket API token email neccessary; for other providers a freely chosen label is fine).

  • Add your token and click “Add token.”

Add URL

  • Select the URL type (Repository or Workspace).

  • Choose a token with the necessary permissions.

  • When you’re viewing the repository or workspace in your browser, copy its URL. (the app automatically normalizes your URL so it can be queried via the API)

  • Click “Add URL.”

Tip: If you already used the URL in another panel you can use the select already used repository/workspace button to easily find the URL again.

g1.png

 

 

Step 2: Select a view (and repository)

Select View

  • Choose one view to display your Git data.

  • Multi-repo views (e.g., Latest commits, Top contributors, Latest pipeline) show all configured repositories.

  • Single-repo views (Repository details, Files, Single file) work with one repository only. If you pick one, go to the next step to select the specific repo (and file).

Further Steps for Single-Repo Views

Select a single repository which you want to diplay

s1.png

 

 

  • If you chose ‘Single file view’ you have to choose which file of the selected repository you want to display

  • Either directly insert the path to the file or click on the folder icon and search for the file manually

  • Click on the file you want to display so that the path is shown in the field

s2.png

 

 

Finish

  • Only one view per macro.

  • When finished, publish or update the page to make the macro visible.

The macro updates automatically according to the activities of the displayed repositories.

 

g2.png

 

 

 

How to completely delete the Macro?

 

Why? When a page or macro is deleted we can’t delete the data saved for this app automatically due to limitations of Confluence.

Delete data completely / wipe everything at once

  • In Confluence, go to Settings → go to Apps → Choose git Insights for Confluence to open the app’s admin panel.

  • Use the “Clear data” buttons:

    • The button next to the macros clears the URLs.

    • The button next to the table with the User data clears the tokens.

g3.png

 

 

g4.png

 

 

 

How to create an Access Token?

General Information

  • Only the token itself and not its name will be relevant for Git Insights

  • After creating the Token: Copy it once and store it securely in you password manager. (Becasue you’ll later see only its name and expiry, not the token value).

  • Set a sensible expiration date (e.g., 1 year). Platforms usually email you before it expires so you can renew in time.

  • Name tokens clearly, e.g., “Git Insights – read-only”. When the expiry email arrives, you’ll know to renew the token on the platform and update it in the macro.

  • Updating in Git Insights: Use Update token in the macro instead of creating a completly new token, so you don’t have to re-enter all URLs/workspaces.

 

g5.png

 

Bitbucket

Bitbucket Cloud supports two ways to authenticate since Sep 9, 2025:

  • Access tokens – created in Bitbucket (repo/workspace level).

  • Atlassian API tokens (with scopes) – created in your Atlassian account and granted to Bitbucket.

Access tokens are intended to be scoped (usually to a single repository if you do not have Bitbucket Premium). In some setups we’ve observed that a token may read other repositories in the same workspace depending on workspace permissions. Verify scope in your environment.

API token with scope

  1. Log in to your Atlassian account → Account Settings

g6.png

 

  1. Security → API tokens → Create and manage API tokens → Create API token with scopes.

g7.png

 

  1. Name + expiry → App: Bitbucket.

  2. Filter by Scope actions: Read and add: read:repository, read:pipeline.

g8.png
g9.png

 

 

  1. Generate and copy the token.

 

Access Token

  1. Open the target repository → Repository settings.

g10.png

 

  1. Under Security, choose Access tokens → Create access token.

g11.png

  1. Name + expire

  2. Scopes: Reposiotory: Read, Pipeline: Read

g12.png

  1. Create, copy and save the token

 

GitHub

We recommend the Fine-grained Token, choosing the classical Token is also possible but less safe.

  1. Profile(top right) → Settings →

g13.png

  1. scroll down to Developer settings → Personal access tokens → Fine-grained tokens → Generate new token.

11.png

  1. Name + expiry → choose repositories (is already only a read-only access unless you manually add other permissions).

g14.png

 

  1. Generate and copy the token.

GitLab

  1. Avatar (top left) → Edit profile → Access tokens → Add new token.

g15.png

 

  1. Name + expiry.

  2. Scopes: read_repository, read_api.

g16.png

 

  1. Create and copy the token.

Azure DevOps

  1. User settings (next to your avatar) → Personal access tokens → New Token.

g17.png
g18.png

 

 

  1. Name + expiry.

  2. Scopes: Code: Read, Build: Read, Release: Read.

g19.png

 

  1. Create and copy the token.