You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing an issue with a repository (namastack-outbox) that belongs to our organization (namastack).
Since yesterday evening, the repository appears to be in a broken or inconsistent state:
The repository was previously public, but is now no longer accessible anonymously (returns 404).
Other organization members who should have access are unable to see or access the repository via the GitHub UI.
Direct links to Issues and Pull Requests still work, but the overview pages (e.g. /issues, /pulls) do not load correctly.
Despite this, Git operations (clone, pull, push) continue to work normally via the CLI and IDE.
This suggests the repository still exists and permissions are partially intact, but visibility and UI access are inconsistent or broken.
We have not intentionally changed repository visibility or access settings. We are unsure whether this is caused by:
an internal error,
a permissions/organization policy issue,
or an automated restriction/flag applied to the repository.
RepositoriesThe core of version-controlled code storagesource:uiDiscussions created via Community GitHub templates
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
Body
I am experiencing an issue with a repository (namastack-outbox) that belongs to our organization (namastack).
Since yesterday evening, the repository appears to be in a broken or inconsistent state:
The repository was previously public, but is now no longer accessible anonymously (returns 404).
Other organization members who should have access are unable to see or access the repository via the GitHub UI.
Direct links to Issues and Pull Requests still work, but the overview pages (e.g. /issues, /pulls) do not load correctly.
Despite this, Git operations (clone, pull, push) continue to work normally via the CLI and IDE.
This suggests the repository still exists and permissions are partially intact, but visibility and UI access are inconsistent or broken.
We have not intentionally changed repository visibility or access settings. We are unsure whether this is caused by:
Beta Was this translation helpful? Give feedback.
All reactions