gitlab-ci: Use 'ref:' on flatpak_ci_initiative.yml for CI safety
Not making use of 'ref:' makes GitLab fetch the latest version of
the *initiative.yml with the latest fixes and such. That would
not be a problem and even desirable maintenance-wise but that
allows GNOME to add anything on our .gitlab-ci.yml at any time.
This is hard to debug and can break our CI. For example,
see: https://gitlab.gnome.org/GNOME/citemplates/-/issues/35.
(cherry picked from commit 459090836a)
This commit is contained in:
parent
a31d0243f1
commit
d71e8ffa00
1 changed files with 3 additions and 2 deletions
|
|
@ -807,8 +807,9 @@ dist-appimage-weekly:
|
|||
expire_in: 8 days
|
||||
|
||||
include:
|
||||
project: 'GNOME/citemplates'
|
||||
file: 'flatpak/flatpak_ci_initiative.yml'
|
||||
project: GNOME/citemplates
|
||||
file: flatpak/flatpak_ci_initiative.yml
|
||||
ref: 42fbc2526a7680b6a4f284a210e63e3973ea6dae
|
||||
|
||||
dist-flatpak-weekly:
|
||||
extends:
|
||||
|
|
|
|||
Loading…
Reference in a new issue