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 02bc2afd
-
mentioned in merge request to-be-continuous/samples/python-docker-compose!6 (merged)
-
mentioned in merge request to-be-continuous/samples/python-on-kubernetes!61 (merged)
-
mentioned in merge request sylvainOL/test-project!5
-
mentioned in merge request sylvainOL/test-project!7
-
mentioned in merge request sylvainOL/test-project!9
Please register or sign in to comment