Bitbucket integration not working with self-hosted instance

[dnaka91]

Is there an existing issue for this?

• I have searched the existing issues

Description of the bug

The Bitbucket integration mentions that the API endpoint can be changed with a env var, but that won't work as self-hosted instances use a completely different REST API compared to the cloud version.

It seems Atlassian splits the APIs between Cloud and Server (self-hosted). Definitely the Cloud version looks much more like a newer and simple API, so I guess they kept the old API for self-hosted instances for backward compatibility.

Therefore, a dedicated extra remote is needed that can handle the older API.

I already prepared the changes locally, but wanted to create an issue for it as well so it can be tracked an associated later.

Steps To Reproduce

1. Have a self-hosted instance of Bitbucket
2. Create project
3. Run git-cliff with the repo configured for the bitbucket integration
4. All API requests fail

Expected behavior

The API requests should work as expected and git-cliff associate the PRs with commits.

Screenshots / Logs

No response

Software information

• Operating system: Arch Linux
• Rust version: 1.79.0

Additional context

No response

[welcome]

Thanks for opening your first issue at git-cliff! Be sure to follow the issue template! ⛰️

[orhun]

Ah, didn't realize that self-hosted instances were using a different API. Thanks for trying it out and creating an issue!