Repository main page returns 404 but other repo pages are accessible #174492
-
Select Topic AreaBug GitHub Feature AreaRepositories BodyI'm experiencing an issue where I can access most parts of a repository I have admin access to, but the main repository page returns a 404 error. Repository Access:
Problem:
Unexpected Workaround: When I navigate to the branches page first, then click the "Code" tab, I can successfully access the main repository page. But direct URL access still fails. Expected Behavior: The main repository page should be accessible directly via https://github.com/user/repo The flow is:
And it’s not just me that I’ve experienced this, the host of the repo (organization) also have the same problem. I mentioned the repo URL, but there are also other ones where I've encountered the same issue - /settings for example. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments · 2 replies
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Hey there! 👋 Thanks for posting in the GitHub Community, @PedroVMota ! We're happy you're here. You are more likely to get a useful response if you are posting in the applicable category. The Accessibility category is a place for our community to discuss and provide feedback on the digital accessibility of GitHub products. Digital accessibility means that GitHub tools, and technologies, are designed and developed so that people with disabilities can use them. I've gone ahead and moved this to the correct category for you, |
Beta Was this translation helpful? Give feedback.
-
|
Ohh you right thank you! |
Beta Was this translation helpful? Give feedback.
-
|
We have recently faced this same issue, the problem was that an import was missing in one of the files from the branch we attempted to merge with main. To solve it we created a new branch from the latest stable commit in main (new-main), merged the branch again, and carefully reviewed all merge conflicts until we found the missing import. For some reason the error was not being flagged anywhere for us, and in trying to push the merged main branch to git it broke. The issue with the 404 errors happens because main is the default branch, so when you go into your repo it tries to read it, fails and throws the error. If you had not figured it out yet, I hope this helps! |
Beta Was this translation helpful? Give feedback.
-
|
I understand. Well, today, Friday the 3rd, I haven't faced any issue until now—it was probably just a problem with GitHub itself, because we haven't done anything and it was solved. But that solution would have helped. I don't have the problem anymore, but if I had it, I would try that. |
Beta Was this translation helpful? Give feedback.
-
|
It happened again. but its worse |
Beta Was this translation helpful? Give feedback.
We have recently faced this same issue, the problem was that an import was missing in one of the files from the branch we attempted to merge with main.
To solve it we created a new branch from the latest stable commit in main (new-main), merged the branch again, and carefully reviewed all merge conflicts until we found the missing import. For some reason the error was not being flagged anywhere for us, and in trying to push the merged main branch to git it broke.
The issue with the 404 errors happens because main is the default branch, so when you go into your repo it tries to read it, fails and throws the error.
If you had not figured it out yet, I hope this helps!