[cli] Fix comments project scope in monorepos

[julianbenegas]

Summary

Fix vercel comments --project <name> in monorepos.

Problem

Given a monorepo with .vercel/repo.json linking web-app to acme-team, while the CLI's current scope is a personal account:

vercel comments --project web-app
# Error: Project "web-app" was not found in team "personal-account".

The workaround required passing both the team and branch explicitly:

vercel comments --project web-app --scope acme-team --branch feature/sidebar

After this change, local repo metadata resolves the project owner and confirms that the project belongs to the current checkout, so this command selects the correct team and current Git branch:

vercel comments --project web-app

[changeset-bot]

🦋 Changeset detected

Latest commit: 676fedf

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
vercel	Patch

Not sure what this means? Click here to learn what changesets are.

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

[github-actions]

🧪 Unit Test Strategy

Comparing: f196f2e → 676fedf (view diff)

Strategy: Affected packages only

✅ Only testing packages that have been modified or depend on modified packages.

Affected packages - 1 (2%)

1. vercel

Unaffected packages - 48 (98%)

1. @vercel-internals/get-package-json
2. @vercel-internals/ipc-proxy
3. @vercel/aws
4. @vercel/backends
5. @vercel/build-utils
6. @vercel/cervel
7. @vercel/cli-auth
8. @vercel/cli-config
9. @vercel/cli-exec
10. @vercel/client
11. @vercel/config
12. @vercel/connect
13. @vercel/container
14. @vercel/detect-agent
15. @vercel/edge
16. @vercel/elysia
17. @vercel/error-utils
18. @vercel/express
19. @vercel/fastify
20. @vercel/firewall
21. @vercel/frameworks
22. @vercel/fs-detectors
23. @vercel/functions
24. @vercel/gatsby-plugin-vercel-analytics
25. @vercel/gatsby-plugin-vercel-builder
26. @vercel/go
27. @vercel/h3
28. @vercel/hono
29. @vercel/hydrogen
30. @vercel/koa
31. @vercel/nestjs
32. @vercel/next
33. @vercel/node
34. @vercel/oidc
35. @vercel/oidc-aws-credentials-provider
36. @vercel/passport
37. @vercel/python
38. @vercel/python-analysis
39. @vercel/redwood
40. @vercel/related-projects
41. @vercel/remix-builder
42. @vercel/routing-utils
43. @vercel/ruby
44. @vercel/rust
45. @vercel/static-build
46. @vercel/static-config
47. @vercel/vc-native
48. examples

Results

• Unit tests: Only affected packages will run unit tests
• E2E tests: Running in parallel in this workflow
• Type checks: Only affected packages will run type checks

---

This comment is automatically generated based on the affected testing strategy

[github-actions]

📦 CLI Tarball Ready

The Vercel CLI tarball for this PR is now available!

Quick Test

You can test this PR's CLI directly by running:

npx https://vercel-ppknj6pds.vercel.sh/tarballs/vercel.tgz --help

Use in vercel.json

To use this CLI version in your project builds, add to your vercel.json:

{
  "build": {
    "env": {
      "VERCEL_CLI_VERSION": "vercel@https://vercel-ppknj6pds.vercel.sh/tarballs/vercel.tgz"
    }
  }
}

Python Runtime Wheel

A vercel-runtime wheel was also built for this PR.
To use in your Python project builds, also set this environment variable:

VERCEL_RUNTIME_PYTHON="vercel-runtime @ https://vercel-ppknj6pds.vercel.sh/tarballs/vercel_runtime-0.17.0.dev1785192858+676fedf-py3-none-any.whl"

Python Workers Wheel

A vercel-workers wheel was also built for this PR.
To use in your Python project builds, also set this environment variable:

VERCEL_WORKERS_PYTHON="vercel-workers @ https://vercel-ppknj6pds.vercel.sh/tarballs/vercel_workers-0.1.0.dev1785192858+676fedf-py3-none-any.whl"

---

This comment is automatically generated