Skip to content

docs: fix dead stargazers links in README - #3365

Merged
charlypoly merged 1 commit into
browserbase:mainfrom
leom1919:docs/fix-stargazers-links
Nov 4, 2026
Merged

charlypoly merged 1 commit into
browserbase:mainfrom
leom1919:docs/fix-stargazers-links

Conversation

@leom1919

@leom1919 leom1919 commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Motivation

The two “⭐ Star this repo” links in README.md point to https://github.com/browserbase/stagehand/stargazers, which returns 404. GitHub no longer serves the /stargazers page for any repository — verified against vercel/next.js/stargazers and microsoft/vscode/stargazers, which 404 the same way, while repository home pages still return 200.

Changes

In README.md (2 lines):

  • Header badge link (line 22): .../stagehand/stargazers → https://github.com/browserbase/stagehand
  • “How you can help” bullet (line 471): same replacement.

The repository home page is where the Star button lives, so the links keep their intent.

Verification

  • curl -L https://github.com/browserbase/stagehand/stargazers → 404; the replacement URL returns 200.
  • Docs-only change: 2 lines inside existing markdown/HTML links, no code touched.

Note: this PR was prepared with the assistance of an automated agent.


Summary by cubic

Fixes the two "⭐ Star this repo" links in the README by pointing them to the repository home page instead of the /stargazers URL, which returns a 404 (GitHub no longer serves the stargazers page for any repo).

Written for commit 602cca2. Summary will update on new commits.

View guided diff

The two 'Star this repo' links point to
https://github.com/browserbase/stagehand/stargazers, which returns 404
(GitHub no longer serves /stargazers pages for any repository - verified
on next.js and vscode as well). Point both links to the repository home
page instead, where the Star button lives.
@changeset-bot

changeset-bot Bot commented Nov 2, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 602cca2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

This PR is from an external contributor and must be approved by a stagehand team member with write access before CI can run.
Approving the latest commit mirrors it into an internal PR owned by the approver.
If new commits are pushed later, the internal PR stays open but is marked stale until someone approves the latest external commit and refreshes it.

@github-actions github-actions Bot added external-contributor Tracks PRs mirrored from external contributor forks. external-contributor:awaiting-approval Waiting for a stagehand team member to approve the latest external commit. labels Nov 2, 2026
@charlypoly
charlypoly merged commit c82e617 into browserbase:main Nov 4, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

external-contributor:awaiting-approval Waiting for a stagehand team member to approve the latest external commit. external-contributor Tracks PRs mirrored from external contributor forks.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants