Add the ability to change git provider and send notifications about events

[setnemo]

About git providers

Could you tell me if there are any plans to add the ability to change the git provider? I know your codebase a little, but I can already see problems blocking this possibility. In my opinion it would be nice to change the git provider usage like this:

• Create interfaces that describe all the features of the git provider.
• Change the git provider related Github classes to interfaces.
• Add new providers: Gitlab, Bitbucket

This is quite a lot of work, so I would like to discuss the possibility of doing it. For my part, I will try to devote a little time to this on the weekends. I am interested in this update as I can use it to automate workflows at work.

About notifications

I also wanted to discuss the possibility of adding a notification interface to be called after any action with git provider. It would be possible to wrap notification in decorator and send updates about the actions to, for example, Jira. This can even set in settings, and over time, the number of providers where you can send information about the event can be expanded. The easiest way to make it workable is to implement the first provider - webhook provider, that send json with information to url from settings like:
{"action": "create release", "data": {"additional": "additional"}}

[chingor13]

Sorry for the delay in getting to this, we just completed a huge refactor/cleanup in v13.

For abstracting the git provider API calls, that seems doable (albeit a ton of work) assuming the other providers have similar API calls so we can swap providers seamlessly. The main issue is that we use another library we wrote (code-suggester) to create the git tree and open the pull request. That logic does not live in this repo so it would likely be significant work to replicate that functionality (that we may not want to maintain here).

Notifications would really need a design. The exit status of CLI commands or the return type of the public API should be enough to handle further notifications after release-please has run. The GitHub action also provides outputs for you to do stuff in subsequent steps.

[leoandrea7]

@chingor13 Has any progress been made after a year? Thanks

[thomasbtf]

I just had to switch from GitHub to GitLab and are really missing Release Please. Would highly appricted it, if GitLab could be supported 🙏

[edw1nzhao]

Bump - has anyone found an alternative to this at least?

[Paul-DS]

Bump - has anyone found an alternative to this at least?

https://github.com/conventional-changelog/conventional-changelog

[austinrscott]

https://github.com/semantic-release/semantic-release

https://github.com/semantic-release/gitlab

[JoseVSeb]

@chingor13 now that we have Claude Code and Gemini CLI to work the heavy load, maybe take another look at this refactor?

P.S. I am attempting it, but since I don't have a deep understanding of this codebase, I may not succeed.

[nblair2]

Has there been any movement on this? Is the PR from @JoseVSeb a good start? I am interested in applying this to giltab.

[ZeroWiggliness]

I needed it for work. So far it works for everything I threw at it but there are probably issues. See for GitLab CI/CD also:

#2631

[robgonnella]

I ran into this issue too as most of our projects are in Gitlab but I really like the release-please flow.

For anyone interested in an alternative I recently created this project: https://github.com/robgonnella/releasaurus
It works across github, gitlab, and gitea. It's still under development, and I'm still testing as many cases as I can, but most features are fully supported. I'm using it successfully in a few repos in both github and gitlab already. Feedback and contributions are always welcome