Is there a way to list repos in an organization I don't have read access to? #8227

There isn't a gh repo list mode that grants a caller a names-only view of private repositories they cannot access. --visibility private filters the repositories visible to the authenticated identity; it does not add permission to discover other private repositories. Increasing --limit addresses pagination, not access.

GitHub documents private repository access and organization repository roles. As you noted, setting base permissions to read would grant access to the repositories' contents, so it does not provide the separate names-only permission you want.

For the duplicate-project discovery use case, an organization owner could maintain an approved project catalog with the names/descriptions that may be shared with members. The process that refreshes that catalog would need authorized access to the source repositories, and the owner would need to approve which metadata it exposes. The catalog can omit sensitive repositories while leaving their existing access controls intact. That is separate from an ordinary member enumerating hidden repositories through gh.

I checked the current CLI help/manual and GitHub's documented access model, and ran a public-repository listing smoke check. I have not tested this with an owner account in your organization or changed any permissions. AI assistance: written with OpenAI Codex.