Skip to content

[Fix] Support links open the wrong GitHub repository - #77

Merged
edelauna merged 1 commit into
mainfrom
fix/zoo-code-support-links-1p6z9j7oxx0bj
May 13, 2026
Merged

[Fix] Support links open the wrong GitHub repository#77
edelauna merged 1 commit into
mainfrom
fix/zoo-code-support-links-1p6z9j7oxx0bj

Conversation

@roomote

@roomoteroomoteBot commented May 12, 2026

Copy link
Copy Markdown
Contributor

Opened on behalf of Toray Altas. View the task or mention @roomote for follow-up asks.

What problem this solves

Fixes an issue where users in the VS Code webview could still be sent to the old RooCodeInc/Roo-Code repository for bug reports, feature requests, marketplace issue reporting, and the security policy after the Zoo Code handoff.

Why this change was made

The webview still had several hardcoded GitHub support links pointing at the upstream repository. This centralizes those URLs in one shared constants module and updates the affected support surfaces to use Zoo-Code-Org/Zoo-Code.

User impact

Support links in the About screen, Marketplace footer, announcement modal, and error fallback now open the Zoo Code repository and issue templates instead of the old upstream repo.

@roomoteroomoteBot added the roomote:auto-resolve-conflicts Allow Roomote to auto-resolve merge conflicts for this PR label May 12, 2026
@roomote

roomoteBot commented May 12, 2026

Copy link
Copy Markdown
ContributorAuthor

No actionable issues found. See task

@codecov

codecovBot commented May 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@taltas
taltas marked this pull request as ready for review May 12, 2026 21:31

@edelaunaedelauna left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Approved with some minor suggestions

@@ -0,0 +1,8 @@
export const EXTERNAL_LINKS = {
GITHUB_REPO: "https://github.com/Zoo-Code-Org/Zoo-Code",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Would it be worth deriving the issue/template/security URLs from a single repo base URL here? That would keep future repo moves from needing several string updates in the same constants file.

it("links support users to the Zoo Code GitHub repository", () => {
render(<Announcement hideAnnouncement={vi.fn()} />)

expect(screen.getByRole("link", { name: "GitHub" })).toHaveAttribute("href", EXTERNAL_LINKS.GITHUB_REPO)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Since this assertion imports the same constant as the component, would a small constants test with the literal Zoo Code URLs give better coverage for accidental target changes?

@edelauna
edelaunaforce-pushed the fix/zoo-code-support-links-1p6z9j7oxx0bj branch from 9faf3ae to 4131a7bCompareMay 13, 2026 23:08
@edelauna

Copy link
Copy Markdown
Contributor

Going to merge this so that we can focus on remaining changes in #85

@edelauna
edelauna merged commit b49a689 into mainMay 13, 2026
9 checks passed
@edelauna
edelauna deleted the fix/zoo-code-support-links-1p6z9j7oxx0bj branch May 27, 2026 19:32
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

roomote:auto-resolve-conflictsAllow Roomote to auto-resolve merge conflicts for this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@edelauna@taltas