Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Different problem with mirroring / sync #8084
There are many problems with mirroring/sync as described here (last entries): https://discourse.gitea.io/t/external-git-server/1425/13
-> The remote/mirroring repo has absolutely no problems with authentication - it never had. It uses basic authentication (Standard authentication by IIS - NOT "Windows Authentication") With SourceTree, it alway worked. -> So no reason for "read only"... The remote repo was never "read only". We need http basic auth for all, read, write, update, delete, whatever...
After a few day i saw the problem (which is not really) with the "Synchronize" button for remote repo in Gitea:
**_"On the repo main page, there is only 1 entry in vertical direction - even if there are more than 1 commit. So i saw, you have to click on “x Commits” to view all of them…
But the “remote repository is read-only” problem still persists - and no, the remote repo is NOT read-only… how i should done the first (initial) commit when it’s read only…?
And i’m still able to commit on the remote repo when i’m directly connected to it. But not if Gitea is connected to it.
And the http basic auth url stored in gitea works when i copy/paste it to browser bar:
And SourceTree, where i can commit to the repo (directly, no over Gitea) also uses that http basic auth.
So problem 1 i not really a problem, but problem 2 is still unsolved!
How to solve it?
Thank you for your feedbacks,
....ok, so the "remote repo is readonly" is sill present. I can't say it is a bug, but so it seems it is.
Maybe somebody can proof the opposite - that it's not a bug? If yes, i think we can close that issue.
If there are any questions, don't hesitate to ask me.