Thomas Gummerer 8eb8a673b1 properly check if the cache is primed (#15723) ... Before every CI job we currently check whether the Go cache is primed, and if not compile all the tests to prime it. However that check is currently wrong. `steps.setup-go.outputs.cache-hit` is a boolean variable, however we compare it against a string 'true'. Since we are comparing for inequality, this check is always true, so we are always priming the cache, even if it is already primed. Fix this check, so we can only prime the cache when it needs to be and don't waste extra CI time to prime the cache when it already might be. h/t again to @iamricard for noticing that we are taking a long time to prime the cache in some cases.		2024-03-18 14:04:12 +00:00
..
scripts	update go-change to the latest version (#15594)	2024-03-05 12:42:05 +00:00
workflows	properly check if the cache is primed (#15723)	2024-03-18 14:04:12 +00:00
CODEOWNERS	add CODEOWNERS file (#15438)	2024-02-16 11:31:23 +00:00
PULL_REQUEST_TEMPLATE.md	Add routine checks to pull request template	2023-05-12 13:34:19 -07:00