Skip to content

feat(forge): bitbucket cloud#2857

Draft
setchy wants to merge 1 commit intomainfrom
feat/forge-adapter-bitbucket
Draft

feat(forge): bitbucket cloud#2857
setchy wants to merge 1 commit intomainfrom
feat/forge-adapter-bitbucket

Conversation

@setchy
Copy link
Copy Markdown
Member

@setchy setchy commented May 8, 2026

GitHub Copilot led port of basic Atlassify functionality into a new Bitbucket Cloud forge adapter

Signed-off-by: Adam Setch <adam.setch@outlook.com>
@setchy setchy changed the title feat(forger): bitbucket cloud feat(forge): bitbucket cloud May 8, 2026
@github-actions github-actions Bot added the enhancement New feature or enhancement to existing functionality label May 8, 2026
export interface IFormData {
token: Token;
hostname: Hostname;
username?: string;
Copy link
Copy Markdown
Member Author

@setchy setchy May 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we create a new dedicated route for LoginWithBitbucketAPIToken?

Aside: I noticed this component also has conditional Gitea login logic mixed in... perhaps we should split these out into each Forge Adapter for clarity?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed! The current PR ends up with 3-deep ternaries (isBitbucket ? … : isGitea ? … : …) for header text, button label, caption text, docs tooltip, and form structure. Each new forge would multiply that matrix 😬

@setchy setchy added the forge:bitbucket Atlassian Bitbucket Cloud label May 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or enhancement to existing functionality forge:bitbucket Atlassian Bitbucket Cloud

Development

Successfully merging this pull request may close these issues.

2 participants