From 961a7c565ffdbf2d57e980fe61cf49d940de278b Mon Sep 17 00:00:00 2001
From: Arie Peterson <arie@greenhost.nl>
Date: Fri, 2 Aug 2019 16:45:42 +0200
Subject: [PATCH] Document Gitlab disallowing merge when there are no CI jobs

---
 .gitlab-ci.yml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index f0bd07bda..ce9bf6048 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -155,4 +155,5 @@ terminate:
     - python3 -c "import cosmos; cosmos.terminate_droplets_by_name(\"^ci-\", 2)"
   # This job has no `only` (anymore), so will always run. This works around a
   # Gitlab bug: if no job runs at all due to `only`, Gitlab gets confused and
-  # doesn't allow you to merge the MR.
+  # doesn't allow you to merge the MR:
+  # https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html#limitations
-- 
GitLab