99designs / gqlgen / 34877000991
0%
master: 0%

LAST BUILD BRANCH: bench_action
DEFAULT BRANCH: master
Ran
Jobs 1
Files 0
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 0.0%. Remained the same
34877000991

Pull #4333

github

StevenACoffman 
_examples: run go generate in the nested example modules

_examples is its own Go module, and ten of the examples under it are
modules in their own right (large-project-structure/*, mini-habr-with-
subscriptions, multi-entity-tests/*, websocket-initfunc/server). Every
one of them carries a //go:generate directive, but nothing ever ran it:
`go generate ./...` stops at module boundaries, so the sweep wired up in
the root main.go reaches _examples itself and nothing below it.

The directives were therefore decorative, and check-generate could not
see these modules drift. They rot quietly until somebody builds one by
hand -- typically whoever changes an exported runtime signature and then
discovers, well after CI went green, that a checked-in example no longer
compiles.

Add _examples/generate-nested.sh, which walks every nested go.mod and
runs `go generate ./...` inside it, and hang it off a second root
//go:generate. check-generate picks it up with no workflow change, so
these modules are now held to the same standard as the rest of the tree.

Running it immediately updates ten resolver files that had been left at
v0.17.94-dev by the v0.17.95 bump. Note the consequence for releases:
the postrelease version bump now has to run the full sweep, because the
version stamp in each generated resolver file is part of what
check-generate diffs.

Signed-off-by: Steve Coffman <steve@khanacademy.org>
Pull Request #4333: _examples: run go generate in the nested example modules

0 of 0 relevant lines covered (NaN%)

0.0 hits per line

Jobs
ID Job ID Ran Files Coverage
1 34877000991.1 0
0.0
GitHub Action Run
Source Files on build 34877000991
Detailed source file information is not available for this build.