Marcel Märtens 13188b49e1 We noticed multiple CI errors over the last week, e.g. https://gitlab.com/veloren/veloren/-/jobs/4749826609 ... $ if [[ ! "${SCHEDULE_CADENCE}" =~ ${TAG_REGEX} ]]; then # collapsed multi-line command warning: redirecting to https://gitlab.com/veloren/veloren.git/ Locking support detected on remote "origin". Consider enabling it with: $ git config lfs.https://veloren-bot:[MASKED]@gitlab.com/veloren/veloren.git/info/lfs.locksverify true ref weekly:: Error in git rev-list --stdin --objects --not --remotes=origin --: exit status 128 fatal: bad object 11bc48033cf4e6528268f2acd97324e16e118bce error: failed to push some refs to 'https://veloren-bot:[MASKED]@gitlab.com/veloren/veloren' There seems to be a fix proposed here: https://github.com/git-lfs/git-lfs/issues/3977 by running git fetch first. lets try it out. Maybe we need to give it some commandline parameters to optimize in the future		2023-07-27 13:22:06 +02:00
..
build.gitlab-ci.yml	move translations over too	2023-06-27 00:13:01 +02:00
check.gitlab-ci.yml	simply scripts alot, not the null check is necessray because gitlab ci regex with variables is weird and would contain errors otherwise.	2022-04-24 10:41:35 +02:00
publish.gitlab-ci.yml	We noticed multiple CI errors over the last week, e.g. https://gitlab.com/veloren/veloren/-/jobs/4749826609	2023-07-27 13:22:06 +02:00
recompile.yml	Make CI trigger on .ftl changes	2022-08-19 18:29:47 +03:00
release.yml	simply scripts alot, not the null check is necessray because gitlab ci regex with variables is weird and would contain errors otherwise.	2022-04-24 10:41:35 +02:00