summaryrefslogtreecommitdiff
path: root/.editorconfig
diff options
context:
space:
mode:
authorPeter Hutterer <peter.hutterer@who-t.net>2024-04-30 08:43:55 +1000
committerPeter Hutterer <peter.hutterer@who-t.net>2024-04-30 08:46:00 +1000
commit414757317d6d1b370fbd38d87ce4bf2802e40809 (patch)
treeb7157c6b424f05fac21c8dd2ba9a678c0ce26214 /.editorconfig
parentfb5402020ff77f455f777477e1638b8fe7b0bd19 (diff)
gitlab CI: don't run MR pipelines in forks
Commit originally by Simon Ser in wayland/wayland-protocols!305. Currently our CI setup has a downside: for each push on a merge request, two pipelines are triggered. The first is triggered in the context of the forked repository, and the second is triggered in the context of the MR in the parent repository. Replace the workflow rules with the ones in the official docs [1], so that a branch pipeline isn't triggered when a MR exists for that branch. [1]: https://docs.gitlab.com/ee/ci/yaml/workflow.html#switch-between-branch-pipelines-and-merge-request-pipelines Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Diffstat (limited to '.editorconfig')
0 files changed, 0 insertions, 0 deletions