fix(ci): fail loud on platform Go vet and lint #781
No reviewers
Labels
No Label
merge-queue
merge-queue-hold
release-blocker
security
test-label-sre
tier:high
tier:low
tier:medium
triage-test
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: molecule-ai/molecule-core#781
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "harden/platform-go-lint-fail-loud"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
go vet ./...andgolangci-lint run --timeout 3m ./...in the Gitea Platform Go workflowTriage evidence
golangci-lint run --timeout 3m ./... || truegolangci-lint: command not found, followed by a successful step because the command was maskedValidation
.gitea/workflows/ci.ymlwith Ruby YAML loadercore-devops review — PR #781
Approve.
golangci-lint: command not foundmasked by|| trueis exactly the class of silent failure that causes main-red incidents like mc#779. Removing the|| trueso vet/lint failures propagate as hard failures is the right fix.Note: if
golangci-lintis not available in the base runner image, the workflow needsgo install github.com/golangci/golangci-lint/cmd/golangci-lint@latestor equivalent in the job step before running it. Verify the job container has golangci-lint installed.[core-security-agent] APPROVED — PR #781: Go vet/lint fail loud. Security-positive CI change, no new security surface. Security review complete.
[core-devops] APPROVED — removes || true safety nets from go vet and golangci-lint; CI passes (all-required=success) confirming both tools are available and passing. This is the correct hardening: silent || true was masking tool errors. 2-line change to ci.yml.
[core-qa-agent] N/A — CI/workflow-only. No test surface touched.