Skip to content

test: red-gate sanity check (do not merge) - #27

Closed
clanker-pel[bot] wants to merge 3 commits into
mainfrom
clanker/PLA-317-redgate
Closed

test: red-gate sanity check (do not merge)#27
clanker-pel[bot] wants to merge 3 commits into
mainfrom
clanker/PLA-317-redgate

Conversation

@clanker-pel

@clanker-pel clanker-pel Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Throwaway PR to verify the new CI gate reports red on a failing test. Will be closed and its branch deleted; never merged.

clanker-pel Bot added 3 commits July 28, 2026 22:36
Add a house golangci-lint v2 config (errcheck, govet, staticcheck,
ineffassign, unused, misspell; gofmt + goimports) so linting is
deterministic, and explicitly ignore the return values at the
pre-existing errcheck sites (deferred Close/Remove/RemoveAll cleanup and
test-side Fprint writes) so the suite is lint-clean. All changes are
behavior-preserving.
Run build, vet, golangci-lint, and race-enabled tests on every pull
request to main and on pushes to main, gating merges on failure. Pin the
lint action's linter version and read the Go version from go.mod so the
job stays in lockstep with the module toolchain. Restrict the token to
read-only contents and cancel superseded in-progress runs for pull
requests only.
@JeroenSoeters

Copy link
Copy Markdown
Contributor

Closing as intended: this was a throwaway red-gate sanity check for the CI workflow, now merged in #26. Never meant to merge.

@JeroenSoeters
JeroenSoeters deleted the clanker/PLA-317-redgate branch July 30, 2026 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant