libinput/.gitlab-ci
Peter Hutterer ace22ad0b0 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

Part-of: <https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/993>
2024-04-29 14:50:07 +10:00
..
ci.template gitlab CI: don't run MR pipelines in forks 2024-04-29 14:50:07 +10:00
config.yml ci: bump to Fedora 39 and FreeBSD to 13.2 2024-03-18 12:31:59 +10:00
libinput.spec.in tools: add a libinput list-kernel-devices tool 2022-12-08 10:08:44 +10:00
meson-build.sh CI: add a comment to the meson build helper 2023-05-30 15:17:14 +10:00
scanbuild-plist-to-junit.py gitlab CI: add a JUnit XML report for scan-build 2021-05-12 13:31:42 +10:00
scanbuild-wrapper.sh gitlab CI: add a JUnit XML report for scan-build 2021-05-12 13:31:42 +10:00
start-in-systemd.sh gitlab CI: explicitly run the test in the systemd service 2023-02-13 09:43:47 +10:00