tree 3e2f1e8dbc56fc57bed8f1e3288a10ead0c9c041
parent 8d537aac8da50e37d27b3e4be401e3819fa95eb4
author Paul Jolly <paul@myitcv.io> 1612189987 +0000
committer Paul Jolly <paul@myitcv.org.uk> 1612360631 +0000

ci: refactor CI setup

The current CI setup is complicated by the fact that we try to place
go:generate directives in the directory (package) where the result is
generated.

This cannot really be satisfied because one of the generation targets is
$modroot/.github/workflows. Per golang.org/issue/43985 this conflicts
with the fact that go generate ./... would not cover such a target, and
hence we need to wrap that go:generate directive in another that would
be covered by ./... - which is messy.

So instead:

* consolidate all CI-related CUE tools in internal/ci
* use go:generate directives in internal/ci for all CI-related
  generation, wrapping the CUE tools

This is in preparation for changes that ensure we have go test coverage
of the various GitHub workflow steps (import, validate, etc).

So now if you:

* change the workflow definitions in internal/ci, or
* pin to a later version of the GitHub workflow schema

just run:

    go generate ./internal/ci

Change-Id: Idbc548c195746f5e021b5a0c1f3ad8773c5fa05f
Reviewed-on: https://cue-review.googlesource.com/c/cue/+/8481
Reviewed-by: CUE cueckoo <cueckoo@gmail.com>
Reviewed-by: Marcel van Lohuizen <mpvl@golang.org>