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).
Loading
-
mentioned in commit 7c3770e3
-
mentioned in merge request to-be-continuous/samples/python-serverless-on-aws!145 (merged)
-
mentioned in merge request to-be-continuous/samples/golang-cnb-helm-on-kubernetes!67 (merged)
-
mentioned in merge request to-be-continuous/samples/golang-cnb-on-kubernetes!70 (merged)
-
mentioned in merge request to-be-continuous/samples/angular-on-s3!229 (merged)
-
mentioned in merge request to-be-continuous/samples/golang-on-cloudfoundry!68 (merged)
-
mentioned in merge request to-be-continuous/samples/golang-docker-on-aws!118 (merged)
Please register or sign in to comment