1.17 breaking changes episode 1: preserving a custom gitconfig
[core] quotePath = false
However, if an Gitea installation was done differently and
$HOME/.gitconfig has been customized because it is shared by a user or another application, there is a good chance that manual modifications were done such as:
[user] name = Jane Doe email = firstname.lastname@example.org
It is also possible that the file was modified manually by the Gitea admin for other reasons. In both there is a potential for breakage when upgrading to Gitea >= 1.17 because the location of the file changed. It must be moved manually to the new location as follows:
- Figure out the directory where
$HOME/.gitconfigmust be moved by running the doctor:
$ gitea --work-path /app/gitea -c /data/gitea/conf/app.ini doctor  Check paths and basic configuration - [I] Configuration File Path: "/data/gitea/conf/app.ini" - [I] Repository Root Path: "/data/git/repositories" - [I] Data Root Path: "/data/gitea" - [I] Custom File Root Path: "/data/gitea" - [I] Work directory: "/app/gitea" - [I] Log Root Path: "/data/gitea/log" OK
- Copy the
$HOME/.gitconfigfile to the Repository Root Path (which is
/data/git/repositoriesin the example above).
The reason why this breaking change was introduced is to workaround a rare problem impacting Gitea installations relying on networked volumes.