How to resolve the issue of the release page displaying incorrectly? #179838
-
Select Topic AreaQuestion BodyWhen not logged in, accessing the releases page of my repository displays all releases correctly. After logging in, accessing the releases page displays "There aren’t any releases here." However, if the releases page URL includes "?page=2", all releases are displayed correctly. I've already submitted two support tickets for automatic closure. The first reply said the free plan doesn't support this, and the second reply said it's an issue about releasing inactive usernames and they're no longer accepting solutions. Clearly, both tickets were misjudged. Could it be that I chose the wrong theme when submitting the ticket? Which theme should I have chosen? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
That’s a GitHub UI bug on their side, not something you can fix. To get the right team, open a support ticket under Repositories Click Releases and include your repo link and screenshots of the empty view vs ?page=2. That sends it to the correct engineering team instead of billing. |
Beta Was this translation helpful? Give feedback.
-
|
Hi. Was this issue resolved? I also experienced this just today |
Beta Was this translation helpful? Give feedback.
-
|
Just to add to this as the repo I am one of the administrators for faced a similar issue, where first page only showed one release, the second and third pages reported "no releaes" but the 4th page onwards started showing the rest of them. Contacted GitHub support using "Restore deleted data -> Other" as the starting point, used "releases not being shown" as the subject title and clearly told them it was a release index issue and provided screenshots of how it was exhibiting as a pagination issue, and they resolved it within an hour. Much obliged for this thread as it gave me the necessary info to get this to the right area and promptly resolved. |
Beta Was this translation helpful? Give feedback.
That’s a GitHub UI bug on their side, not something you can fix. To get the right team, open a support ticket under Repositories Click Releases and include your repo link and screenshots of the empty view vs ?page=2. That sends it to the correct engineering team instead of billing.