Skip to content

feat: support alternatively specified merge strategies for bitbucket #6022

Open
Open
feat: support alternatively specified merge strategies for bitbucket#6022
Labels
area/controllerAffects the (main) controllerkind/enhancementAn entirely new featurekind/proposalIndicates maintainers have not yet committed to a feature requestneeds discussionA maintainer explicitly requests no action be taken without further discussionneeds researchAction on the issue is blocked, pending researchpriority/lowLow commitment from maintainers; progress is likely to be community-driven
@fuskovic

Description

@fuskovic
fuskovic
opened on Apr 1, 2026

go-bitbucket does not expose the merge method/strategy as an option. The merge will always use the repository's default merge strategy, so we are currently failing if any merge strategy was specified. This is strictly a limitation of the go-bitbucket library and not the Bitbucket API itself.

See TODO left on pkg/gitprovider/bitbucket/bitbucket.go/MergePullRequest from #5581

Proposed Feature

We can wait for the library to support for this or if we decide to implement this API call ourselves instead of using the library.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/controllerAffects the (main) controllerkind/enhancementAn entirely new featurekind/proposalIndicates maintainers have not yet committed to a feature requestneeds discussionA maintainer explicitly requests no action be taken without further discussionneeds researchAction on the issue is blocked, pending researchpriority/lowLow commitment from maintainers; progress is likely to be community-driven

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions