ci: add GitHub Actions workflow - #26
Closed
mgilbir wants to merge 1 commit into
Closed
Conversation
Build, vet, and the -short regression suite (600+ specs) plus golangci-lint on every push and pull request. All inputs are committed (vendored JS modules, WASM binaries, test data), so the workflow needs no network beyond toolchain setup (audit C18).
Owner
Author
|
Dropping — GitHub Actions not wanted for this repo. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #25.
The repo carries a 600+-spec regression corpus, RMSE-based PNG comparison, injection tests, and a version-sync test — and nothing ran them on push.
Adds a workflow running build,
go vet, andgo test -short ./...(skips only the slow geo/TopoJSON specs) plusgolangci-lint(verified clean locally) on every push to main and every PR. All inputs are committed — vendored JS modules, both WASM binaries, test data — so the jobs need no network beyond toolchain setup. This depends on the previous PR in the stack, which decoupled the test targets from re-vendoring.Audit: C18.