Daniel FarrellandThomas Pantelis eea398da4e Use SHAs for GHA versions ...

Per GitHub's security guidelines, GHAs should be pinned using full
length commit SHAs instead of tags.

The SHAs are of the commits currently resolved by the versions.

Even "trusted" GHAs from GitHub developers are pinned because it's
possible their repo rights could be compromised and a malicious GHA
published. These core repos are not frequently substantially updated.

Submariner-internal GHAs are left pinned at devel because we want
automatic updates from Shipyard's shared tooling.

Signed-off-by: Daniel Farrell <dfarrell@redhat.com>

2021-08-24 08:18:22 -04:00

..

branch.yml

Add a failing check on PRs not targeting devel

2021-04-05 13:26:24 -04:00

dependent-issues.yml

Don't run periodic PR dependency checks on forks

2021-08-09 16:39:00 -04:00

e2e-full.yml

Use SHAs for GHA versions

2021-08-24 08:18:22 -04:00

e2e.yml

Use SHAs for GHA versions

2021-08-24 08:18:22 -04:00

flake_finder.yml

Use SHAs for GHA versions

2021-08-24 08:18:22 -04:00

linting.yml

Use SHAs for GHA versions

2021-08-24 08:18:22 -04:00

periodic.yml

Use SHAs for GHA versions

2021-08-24 08:18:22 -04:00

release.yml

Use SHAs for GHA versions

2021-08-24 08:18:22 -04:00