Feature Request: Add Bitbucket Support for Supabase Branching

[hugo-ribaud]

Feature Request: Add Bitbucket Support for Supabase Branching

Problem Description

Currently, Supabase's branching feature only supports GitHub repositories, which creates a significant barrier for teams using Bitbucket as their primary version control system. Many enterprise organizations, particularly those invested in the Atlassian ecosystem (Jira, Confluence, Bitbucket), cannot leverage Supabase's powerful database branching capabilities without switching their entire version control infrastructure.

This limitation forces teams to either:

• Maintain separate workflows for database development
• Consider switching version control providers
• Abandon Supabase branching altogether

Proposed Solution

Extend Supabase branching to support Bitbucket repositories with feature parity to the current GitHub integration:

1. Automatic branch creation when new Bitbucket branches are created
2. Preview environments for Bitbucket pull requests
3. Webhook integration for automatic deployment and updates
4. Status reporting directly in Bitbucket pull requests
5. Migration execution and data seeding for preview branches
6. CLI support for Bitbucket-based workflows

Why This Matters

Market Impact

• Approximately 30% of enterprise development teams use Bitbucket
• Strong presence in regulated industries (finance, healthcare, government)
• Deep integration with Atlassian suite drives organizational adoption

Technical Feasibility

Supabase already has Bitbucket integration experience:

• ✅ Bitbucket OAuth provider for authentication
• ✅ CI/CD support for Edge Functions deployment
• ✅ Existing webhook handling infrastructure

This suggests the technical foundation already exists for deeper Bitbucket integration.

Competitive Advantage

Very few database platforms offer multi-provider git integration. Supporting Bitbucket would:

• Differentiate Supabase in the enterprise market
• Remove a common objection in enterprise sales cycles
• Demonstrate commitment to platform flexibility

Use Cases

1. Enterprise Teams: Organizations using Jira + Confluence naturally use Bitbucket for code
2. Multi-Provider Environments: Companies with repositories across different providers
3. Migration Scenarios: Teams transitioning between providers need continuity
4. Compliance Requirements: Some organizations mandate specific git providers

Technical Implementation Approach

Building on Supabase's existing architecture:

Phase 1: Core Integration (MVP)

• Repository connection via Bitbucket OAuth
• Branch synchronization using Bitbucket webhooks
• Basic branch creation/deletion operations

Phase 2: Pull Request Integration

• Handle pullrequest:created, pullrequest:updated events
• Implement status reporting to Bitbucket PRs
• Support for preview URLs in PR comments

Phase 3: Feature Parity

• Monorepo support with custom paths
• Persistent branches for long-running features
• Edge Function deployment integration
• Advanced configuration options

Key Technical Differences to Address

Feature	GitHub	Bitbucket
Authentication	OAuth 2.0 + GitHub Apps	OAuth 2.0 + Atlassian accounts
Webhooks	push, pull_request	repo:push, pullrequest:created
API Structure	/repos/{owner}/{repo}/	/repositories/{workspace}/{repo_slug}/
Status API	Checks API	Build status API

Community Support

This request aligns with Discussion #18936 where Bitbucket is listed as "under consideration". Multiple community members have expressed interest in this feature for their enterprise deployments.

Commitment to Contribute

Our team is willing to:

• Provide detailed Bitbucket API documentation and examples
• Beta test the integration with production workloads
• Contribute to documentation and tutorials
• Share implementation feedback with the community

Alternative Considerations

If full Bitbucket support isn't immediately feasible, consider:

1. Generic webhook interface allowing custom integrations
2. Branch API enabling third-party tools to trigger branch operations
3. Import/export utilities for migration between providers

Success Metrics

• Adoption rate among existing Supabase customers using Bitbucket
• Reduction in provider-switching as adoption barrier
• New enterprise customer acquisitions
• Community engagement and contributions

References

• Supabase Branching Documentation
• Discussion #18936: Git Provider Options
• Existing Bitbucket OAuth Support

---

Thank you for considering this feature request. Bitbucket support would significantly expand Supabase's reach in the enterprise market and demonstrate the platform's commitment to supporting diverse development workflows.