fix(workflow): disable MR pipeline from prod & integ branches
Today creating a backmerge MR from prod or integ branch to any other branch triggers a pipeline even though no change has been pushed. Ultimately those pipelines might (re)trigger integration or production environment deployment and/or packages publication. That might have unexpected consequences. This change simply disables MR pipeline from prod & integ branches, enforcing branch pipelines only (i.e. when a true commit is pushed).
-
mentioned in commit ac8fcbe8
-
mentioned in merge request to-be-continuous/samples/python-docker-compose!6 (merged)
-
mentioned in merge request to-be-continuous/samples/python-on-azure!48 (merged)
-
mentioned in merge request to-be-continuous/samples/python-helmfile-on-kubernetes!72 (merged)
-
mentioned in merge request to-be-continuous/samples/python-on-kubernetes!61 (merged)
-
mentioned in merge request to-be-continuous/samples/freepascal-make-helm!29 (merged)
-
mentioned in merge request to-be-continuous/samples/golang-cnb-helm-on-kubernetes!58 (merged)
-
mentioned in merge request to-be-continuous/samples/golang-cnb-on-kubernetes!60 (merged)
-
mentioned in merge request to-be-continuous/samples/maven-on-openshift!59 (merged)
-
mentioned in merge request to-be-continuous/samples/python-serverless-on-aws!145 (merged)
-
mentioned in merge request to-be-continuous/samples/golang-docker-on-aws!90 (merged)
-
mentioned in merge request to-be-continuous/samples/maven-on-gcloud!104 (merged)
-
mentioned in merge request to-be-continuous/samples/maven-on-kubernetes!112 (merged)