-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Promotion / create PR feature for Bitbucket server #2569
Comments
This isn't a high priority for the maintainers at the moment, but we would fully support this. It's an issue of medium difficulty and we would welcome someone from the community to pick it up and run with it. |
I would like to take this, and thinking to use this https://github.com/ktrysmt/go-bitbucket (if maintainers are agree) or BitBucket API |
No objection to that package. |
Awesome. I'll start working on it |
Hey @chamodshehanka, any news regarding the development of the Bitbucket PR functionality? Do you still plan to do it? |
yes. Can I open a draft PR? |
That would be awesome! But, for more context: we are also evaluating Kargo for our company and our initial impression is good. However, we really need Bitbucket PR support, which is why I was asking you if you'll add support for it. |
that's great! we could work together then |
Calling attention to #3128 which is an in-progress PR to add Azure DevOps support. It's a good example of how support for a new Git provider is added. |
Hi @krancour , after reading the issue I get for Azure Devops and Bitbucket is community made right? In my case is Gitea integration, would it follow the same proccedure? Thanks in advanced! |
Yes. Support for any/all Git hosting providers all should implement the same interface. |
We are currently evaluating Kargo and we would like Kargo to have a feature to open up Pull requests to Bitbucket server for our prod staging promotion process. We see that Kargo has a feature to support GitHub and GitLab, but not BB server. Is that some thing that can be added in the future releases , that will enable us to get going with Kargo.
The text was updated successfully, but these errors were encountered: