Forking creates a new project with empty repository on current master
Summary
When creating a fork on current master (4a4f8093), instead of copying the repository, an empty one is displayed.
Steps to reproduce
- log in as user without gitlab-ce project
- click fork
What is the current bug behavior?
Empty repository:
What is the expected correct behavior?
Copy of repository is created.
Logs
15:07:43 gitaly.1 | time="2017-10-04T15:07:43+02:00" level=info msg="finished unary call" grpc.code=OK grpc.method=RepositoryExists grpc.request.repoPath="user1/gitlab-ce.wiki.git" grpc.request.repoStorage=default grpc.request.topLevelGroup=user1 grpc.service=gitaly.RepositoryService grpc.time_ms=0 peer.address= span.kind=server system=grpc
15:07:43 gitaly.1 | time="2017-10-04T15:07:43+02:00" level=info msg="finished unary call" grpc.code=OK grpc.method=RepositoryExists grpc.request.repoPath="user1/gitlab-ce.wiki.git" grpc.request.repoStorage=default grpc.request.topLevelGroup=user1 grpc.service=gitaly.RepositoryService grpc.time_ms=0 peer.address= span.kind=server system=grpc
15:07:43 gitlab-workhorse.1 | localhost:3000 127.0.0.1:63070 - - [2017-10-04 15:07:43.632380325 +0200 CEST] "POST /gitlab-org/gitlab-ce/forks?namespace_key=27 HTTP/1.1" 302 103 "http://localhost:3000/gitlab-org/gitlab-ce/forks/new" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36" 0.355086
15:07:44 gitaly.1 | time="2017-10-04T15:07:44+02:00" level=info msg="finished unary call" grpc.code=OK grpc.method=RepositoryExists grpc.request.repoPath="user1/gitlab-ce.git" grpc.request.repoStorage=default grpc.request.topLevelGroup=user1 grpc.service=gitaly.RepositoryService grpc.time_ms=0 peer.address= span.kind=server system=grpc