Philip Withnall 1b391485f6 check: Limit clone depth for clones done as part of CI builds ...

There’s no need to fetch the entire git history for OSTree or malcontent
for each CI job. Do shallow clones and don’t fetch tags. This reduces
the bandwidth requirement for clones in a CI job by roughly a factor of
8.5 (from 19.5MB to 2.3MB)

See https://tecnocode.co.uk/2020/07/09/easily-speed-up-ci-by-reducing-download-size/

This is slightly complicated by the fact that OSTree is currently being
built from a relatively-recent git commit. Once the flatpak CI can
depend on a tagged OSTree release (say, 2020.8),
```
--branch master --shallow-since 2020-10-27
```
can be changed to
```
--branch v2020.8 --depth 1
```

Signed-off-by: Philip Withnall <pwithnall@endlessos.org>

2020-12-12 17:06:40 +00:00

..

block-autosquash-commits.yml

Add action that checks for autosquash commits in pull requests

2019-09-26 13:00:22 +02:00

check.yml

check: Limit clone depth for clones done as part of CI builds

2020-12-12 17:06:40 +00:00