Feature request: give organization members a 403, not 404

As is:

When a repo is private and the collaboration settings are incomplete, an organization member gets a 404 page.

This results in confusion, I’ve had coworkers assume the repo is missing or the link given is incorrect. My guess the 404 is for security and avoids leaking information.


Allow organization members to know the repo exists and they do not have access (403).

Even better would be some copy or a link as to how to ask for access.

If the users is anonymous or not an org member, continue 404’ing.

Hi @beck,

Thanks for this feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.


1 Like