Windows runner fails with git circular include

Summary

When trying to run any build on Windows with 13.3.0 runner it fails when trying to get sources.

Steps to reproduce

Run any build. Multiple projects started failing right after runner was (automatically) updated from 13.2.2 to 13.3.0

Actual behavior

Logs show the following:

Running with gitlab-runner 13.3.0 (86ad88ea)
  on buildnode8 gWCLBA4o

Preparing the "docker-windows" executor
Using Docker executor with image git:4567/docker-visualstudio:2019 ...
Authenticating with credentials from job payload (GitLab Registry)
Pulling docker image git:4567/docker-visualstudio:2019 ...
Using docker image sha256:a63b520c58ce1f651d18845a9e528bdfa11fd70248518ed156d60dffddc068dd for git:4567/docker-visualstudio:2019 ...

Preparing environment
Running on RUNNER-GWCLBA4O via 
buildnode8...

Getting source from Git repository
fatal: exceeded maximum include depth (10) while including
	C:/Program Files/Git/etc/gitconfig
from
	C:/Program Files/Git/etc/gitconfig
This might be due to circular includes.
ERROR: Job failed: exit code 128

The gitconfig file doesn't exist in the docker image. I guess runner creates it on the fly.

Expected behavior

Fetching changes...
Initialized empty Git repository in C:/b/client/.git/
Created fresh repository.
Checking out daa22647 as dev...
git-lfs/2.11.0 (GitHub; windows amd64; go 1.14.2; git 48b28d97)

Environment description

• Windows Server 2019, v1809 (17763.1397)
• Docker 18.09.3, build 142dfcedca
• Git for Windows 2.21