ingress build fails at missing repo

[prsnnkrsh]

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):

What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG

NGINX Ingress controller version: v0.12.0

Kubernetes version (use kubectl version):1.7

Environment:

• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release): debian
• Kernel (e.g. uname -a):4.9.82-1+deb9u3
• Install tools: docker
• Others:

What happened: Trying to build a local image of ingress-controller. While executing build.sh under /images/nginx, build fails to clone the v3/dev/performance branch of the https://github.com/SpiderLabs/ModSecurity repo. Tried to clone the branch manually and got the same error.

Cloning into 'ngx_brotli'...
Submodule 'deps/brotli' (https://github.com/google/brotli.git) registered for path 'deps/brotli'
Cloning into '/tmp/build/ngx_brotli/deps/brotli'...
Submodule path 'deps/brotli': checked out '222564a95d9ab58865a096b8d9f7324ea5f2e03e'
Cloning into 'ModSecurity'...
warning: Could not find remote branch v3/dev/performance to clone.
fatal: Remote branch v3/dev/performance not found in upstream origin
The command '/bin/sh -c chmod 777 /build.sh; ls -lrt /     && sleep 5;ls -lrt /; /build.sh     && ln -sf /dev/stdout /var/log/nginx/access.log     && ln -sf /dev/stderr /var/log/nginx/error.log     && rm -f /build.sh' returned a non-zero code: 128

$ git clone -b v3/dev/performance --single-branch https://github.com/SpiderLabs/ModSecurity
Cloning into 'ModSecurity'...
warning: Could not find remote branch v3/dev/performance to clone.
fatal: Remote branch v3/dev/performance not found in upstream origin

What you expected to happen:
Build to go smoothly.

How to reproduce it (as minimally and precisely as possible):
Try to build the image

Anything else we need to know:
This was working as of Friday 3/31. I worked around it by cloning the master branch instead. Hoping that will not cause any issues.