git >=2.36 is both in 1.16.9 and 1.17
parent
0e9a9c0c6a
commit
8f1791eb74
|
@ -22,8 +22,8 @@ This started to show in the past few weeks to [users running the Gitea binary on
|
||||||
### Workarounds
|
### Workarounds
|
||||||
|
|
||||||
* If using [Gitea docker images](https://hub.docker.com/r/gitea/gitea):
|
* If using [Gitea docker images](https://hub.docker.com/r/gitea/gitea):
|
||||||
* do not upgrade to 1.16.6, 1.16.7 or 1.16.8, or
|
* upgrade to [Gitea >=1.16.9](https://github.com/go-gitea/gitea/pull/19876) or 1.17, both have git >=2.36
|
||||||
* downgrade from 1.16.6, 1.16.7 or 1.16.8 to 1.16.5 (do **not** downgrade from 1.17.x, it may corrupt your the Gitea database)
|
* `git config --global --replace-all safe.directory '*'`
|
||||||
* If the Gitea binary was installed independently of git, upgrade git to a version that is [greater or equal to 2.36](https://git-scm.com/docs/git-config#Documentation/git-config.txt-safedirectory) and disable the security check entirely with:
|
* If the Gitea binary was installed independently of git, upgrade git to a version that is [greater or equal to 2.36](https://git-scm.com/docs/git-config#Documentation/git-config.txt-safedirectory) and disable the security check entirely with:
|
||||||
* impersonate the [user dedicated to Gitea](https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration) (usually git)
|
* impersonate the [user dedicated to Gitea](https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration) (usually git)
|
||||||
* `git config --global --replace-all safe.directory '*'`
|
* `git config --global --replace-all safe.directory '*'`
|
||||||
|
|
Loading…
Reference in New Issue