--- a/contrib/heptapod-ci.yml Mon Jul 03 15:28:17 2023 +0200
+++ b/contrib/heptapod-ci.yml Tue Jul 04 12:21:45 2023 +0200
@@ -3,12 +3,12 @@
# `branch/stable`), but the hash hasn't changed. There is no reason to
# re-run the CI in our case, since we haven't built up any specific automation.
# Right now it's just wasted CI and developer time.
-# One can still run the pipeline manually via the web interface or a push,
+# One can still run the pipeline manually via the web interface,
# like in the case of releases, to make *extra* sure that the actual branch
# has succeeded.
workflow:
rules:
- - if: $CI_COMMIT_BRANCH =~ /^branch\/.*/ && $CI_PIPELINE_SOURCE != "web" && $CI_PIPELINE_SOURCE != "push"
+ - if: $CI_COMMIT_BRANCH =~ /^branch\/.*/ && $CI_PIPELINE_SOURCE != "web"
when: never
- if: $CI_PIPELINE_SOURCE == "merge_request_event"
- if: $CI_COMMIT_BRANCH && $CI_OPEN_MERGE_REQUESTS