What happened
I have Gitblit repositories (bare git repos with data) which I would like to move across to Gitea (I use version: 1.23.6).
Now I have moved some over to for example git/repositories/mzee/TestRepo1.git.
What I noticed is that, unlike Gitblit, Gitea doesn’t straight away show the repository in the web UI. That’s how I pushed all my repos from my NAS samba share based to Gitea a while ago!
And now I want to bring everything to Gitea. I run Gitea on Docker.
What I tried
- Admnin view (
https://mygitea.local/-/admin) based on this post: I clicked “Resynchronize pre-receive, update and post-receive hooks of all repositories.” button in admin panel. - Comparing to another repository that was fully created by Gitea, I can see the hooks are missing in the bare repository I copied over.
Notice in this screenshot, the test1234.git is created once I re-run the hooks via admin. But the repo I copied over and is visible in the UI partly is Test1234 (case difference!). Ignore the test12345.git.
A screenshot of what is visible in the UI:
Question…
My question is what should I do next to get this Test1234 repo content displaying under user mzee in the Gitea web interface?
Similar threads found
- [solved] Git repository updated on disk but commits are not shown in the web interface - Install/Maintain/Configure - Gitea
[solved] Git repository updated on disk but commits are not shown in the web interface - #2 by howl - Gitea web not updating pages correctly - Install/Maintain/Configure - Gitea
Gitea web not updating pages correctly - #13 by fosBHY - Respository’s home page not updated after first push · Issue #3458 · go-gitea/gitea
Respository's home page not updated after first push · Issue #3458 · go-gitea/gitea · GitHub