Skip to main content

Bitbucket Integration 📘

note

If you have built from source, enable the bitbucket feature flag for the integration to work.

For projects hosted on Bitbucket, you can use git-cliff to add the following to your changelog:

  • Bitbucket usernames
  • Contributors list (all contributors / first time)
  • Pull request links (associated with the commits)

Setting up the remote​

As default, remote upstream URL is automatically retrieved from the Git repository.

If that doesn't work or if you want to set a custom remote, there are a couple of ways of doing it:

[remote.bitbucket]
owner = "orhun"
repo = "git-cliff"
token = "***"

  • Use the --bitbucket-repo argument (takes values in OWNER/REPO format, e.g. "orhun/git-cliff")

  • Use the BITBUCKET_REPO environment variable (same format as --bitbucket-repo)

Authentication​

tip

Bitbucket REST API is being used to retrieve data from Bitbucket and it has rate limiting rules.

You can follow this guide for creating an access token.

To set an access token, you can use the configuration file (not recommended), --bitbucket-token argument or BITBUCKET_TOKEN environment variable.

For example:

BITBUCKET_TOKEN="***" git cliff --bitbucket-repo "orhun/git-cliff"
tip

You can use the BITBUCKET_API_URL environment variable want to override the API URL. This is useful if you are using your own Bitbucket instance.

Templating​

tip

See the templating documentation for general information about how the template engine works.

Remote​

You can use the following context for adding the remote to the changelog:

{
  "bitbucket": {
    "owner": "orhun",
    "repo": "git-cliff"
  }
}

For example:

https://bitbucket.org/{{ remote.bitbucket.owner }}/{{ remote.bitbucket.repo }}/commits/tag/{{ version }}

Commit authors​

For each commit, Bitbucket related values are added as a nested object (named bitbucket) to the template context:

{
  "id": "8edec7fd50f703811d55f14a3c5f0fd02b43d9e7",
  "message": "refactor(config): remove unnecessary newline from configs\n",
  "group": "🚜 Refactor",

  "...": "<strip>",

  "remote": {
    "username": "orhun",
    "pr_title": "some things have changed",
    "pr_number": 420,
    "pr_labels": ["rust"],
    "is_first_time": false
  }
}

This can be used in the template as follows:

{% for commit in commits %}
  * {{ commit.message | split(pat="\n") | first | trim }}\
    {% if commit.remote.username %} by @{{ commit.remote.username }}{%- endif %}\
    {% if commit.remote.pr_number %} in #{{ commit.remote.pr_number }}{%- endif %}
{%- endfor -%}

The will result in:

- feat(commit): add merge_commit flag to the context by @orhun in #389
- feat(args): set `CHANGELOG.md` as default missing value for output option by @sh-cho in #354

Contributors​

For each release, following contributors data is added to the template context as a nested object:

{
  "version": "v1.4.0",
  "commits": [],
  "commit_id": "0af9eb24888d1a8c9b2887fbe5427985582a0f26",
  "timestamp": 0,
  "previous": null,
  "bitbucket": {
    "contributors": [
      {
        "username": "orhun",
        "pr_title": "some things have changed",
        "pr_number": 420,
        "pr_labels": ["rust"],
        "is_first_time": true
      },
      {
        "username": "cliffjumper",
        "pr_title": "I love jumping",
        "pr_number": 999,
        "pr_labels": ["rust"],
        "is_first_time": true
      }
    ]
  }
}

This can be used in the template as follows:

{% for contributor in bitbucket.contributors | filter(attribute="is_first_time", value=true) %}
  * @{{ contributor.username }} made their first contribution in #{{ contributor.pr_number }}
{%- endfor -%}

The will result in:

- @orhun made their first contribution in #420
- @cliffjumper made their first contribution in #999