Problem or use case
Currently, Orca provides built-in integration with GitHub, including pull requests, issues, and Actions tied to worktrees. While this is extremely useful, many teams and organizations rely on alternative source control platforms such as GitLab, Bitbucket, or self-hosted Git solutions.
Proposed solution
Add support for additional source control providers, including:
GitLab (cloud and self-hosted)
Bitbucket
Generic Git providers via configurable APIs or plugins
Alternatives or additional context
Given that Orca already includes built-in source control features and GitHub integration, extending this capability to other providers would be a natural next step toward making the IDE more platform-agnostic and developer-friendly.
Problem or use case
Currently, Orca provides built-in integration with GitHub, including pull requests, issues, and Actions tied to worktrees. While this is extremely useful, many teams and organizations rely on alternative source control platforms such as GitLab, Bitbucket, or self-hosted Git solutions.
Proposed solution
Add support for additional source control providers, including:
GitLab (cloud and self-hosted)
Bitbucket
Generic Git providers via configurable APIs or plugins
Alternatives or additional context
Given that Orca already includes built-in source control features and GitHub integration, extending this capability to other providers would be a natural next step toward making the IDE more platform-agnostic and developer-friendly.