What problem are you trying to solve?
We use Bitbucket as our primary Git provider and would like to use OpenKnowledge's Git synchronization capabilities directly with our Bitbucket repositories.
Currently, OpenKnowledge's native Git integration appears to focus on GitHub. For organizations using Bitbucket, this means additional custom integration or synchronization logic is required.
We have a large number of private repositories, so native Bitbucket support would make it much easier to adopt OpenKnowledge as an organization-wide knowledge platform.
Proposed solution
add Bitbucket as a native Git provider, similar to the existing GitHub integration.
Ideally, the integration would support:
Connecting Bitbucket Cloud repositories.
Private repositories.
Authentication using Bitbucket API tokens, OAuth, or another supported authentication mechanism.
Selecting repositories from a Bitbucket workspace/project.
Automatic synchronization when repository content changes.
Manual synchronization when needed.
Branch selection.
Webhook-based synchronization.
Repository/source metadata retained inside OpenKnowledge.
Support for multiple Bitbucket repositories if multi-repository support is introduced.
Area
Other
Alternatives considered
We could clone or mirror Bitbucket repositories into GitHub or into a separate repository supported by OpenKnowledge.
However, this introduces another synchronization layer and requires maintaining duplicate repository infrastructure.
We could also build a custom pipeline that pulls content from Bitbucket and pushes it into OpenKnowledge, but native Bitbucket support would provide a simpler and more maintainable integration.
What problem are you trying to solve?
We use Bitbucket as our primary Git provider and would like to use OpenKnowledge's Git synchronization capabilities directly with our Bitbucket repositories.
Currently, OpenKnowledge's native Git integration appears to focus on GitHub. For organizations using Bitbucket, this means additional custom integration or synchronization logic is required.
We have a large number of private repositories, so native Bitbucket support would make it much easier to adopt OpenKnowledge as an organization-wide knowledge platform.
Proposed solution
add Bitbucket as a native Git provider, similar to the existing GitHub integration.
Ideally, the integration would support:
Connecting Bitbucket Cloud repositories.
Private repositories.
Authentication using Bitbucket API tokens, OAuth, or another supported authentication mechanism.
Selecting repositories from a Bitbucket workspace/project.
Automatic synchronization when repository content changes.
Manual synchronization when needed.
Branch selection.
Webhook-based synchronization.
Repository/source metadata retained inside OpenKnowledge.
Support for multiple Bitbucket repositories if multi-repository support is introduced.
Area
Other
Alternatives considered
We could clone or mirror Bitbucket repositories into GitHub or into a separate repository supported by OpenKnowledge.
However, this introduces another synchronization layer and requires maintaining duplicate repository infrastructure.
We could also build a custom pipeline that pulls content from Bitbucket and pushes it into OpenKnowledge, but native Bitbucket support would provide a simpler and more maintainable integration.