Merge request failure on git-clone step (Gitlab Private Repo)

NOTE: This is the same issue reported here:

  1. Gitlab merge request failure on git-clone step (if PR is sent from a private fork) but it is now closed.
  2. Git-clone fails when PR is sent from private fork (Github)

all GITLAB PR trigger fails on git-clone step

Where did the issue happen?

git "init"
Initialized empty Git repository in /bitrise/src/.git/
git "remote" "add" "origin" ""
git "fetch" "origin" "bitrise"
Warning: Permanently added ',' (ECDSA) to the list of known hosts.
 * branch            bitrise    -> FETCH_HEAD
 * [new branch]      bitrise    -> origin/bitrise
ERROR: auto merge, error: there is no Pull Request branch and can't download diff file
|                                                                              |
| x | git-clone@4 (exit code: 1)                                    | 9.55 sec |
| Issue tracker:          |
| Source:                        |

Description of the issue

Sent a Merge Request from a private repo to a private repo (GITLAB)


Where did the issue happen?

on Android & Docker, on Ubuntu 16.04

Which build Step causes the issue and which version of the step?

Git Clone v4.0.18


  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? : YES
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : Well everytime I file a merge request


is there any alternative solution this issue?

I face similar issue here.
but my case is forked repo merge to upstream repo. (self-hosted GitLab)
all repo’s Project visibility are Internal.

Sorry to hear about the issues! Can you guys please include build URLs with your report? It would really help if we could access the logs completely. Thanks!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.