wxiaoguang 26070eb818 When the git repository on storage is changed, the repository modal should also be updated (#18088) ... User would keep seeing an empty repo if: * An error occurs during the first git pushing/receiving * A user replaces the Gitea's empty repository manually Fix: when a user is viewing the repository web page, if the repoModal.IsEmpty is true, we check the git repository again to detect whether it is really empty. However: the IsEmpty flag is deeply broken and should be removed. For example it's possible for a repository to be non-empty by that flag but still 500 because there are no branches - only tags -or the default branch is non-extant as it has been 0-pushed.		2021-12-24 23:36:26 +08:00
..
api/v1	- name: new parameter in CreateForkOption to give the forked repository (#18066)	2021-12-24 22:43:00 +08:00
common	Update chi/middleware to chi/v5/middleware (#17888)	2021-12-02 21:58:08 +01:00
install
private
utils
web	When the git repository on storage is changed, the repository modal should also be updated (#18088)	2021-12-24 23:36:26 +08:00
init.go