chore(ci): add linting, formatting, and CI pipeline #170
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
thwap/ttheart!170
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/ci-linting-config"
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?
What
Add comprehensive linting, formatting, and CI configuration for the ttheart project:
.pre-commit-config.yaml— automated pre-commit hooks (formatting, vetting, validation).golangci-lint.yml— static analysis with ~35 enabled linters.forgejo/workflows/ci.yml— Forgejo Actions CI pipeline running on all PRs and pushes to mainWhy
Enforce code quality and consistency from the start. All changes must pass pre-commit hooks, golangci-lint, and tests before merge. Catches bugs, style violations, and security issues early.
Testing
Breaking Changes
None.
Notes
Review complete. Solid CI foundation — well-structured jobs, sensible linter selection, good test coverage setup. No blocking issues found.
Suggestions
.forgejo/workflows/ci.yml:31– Pre-commit job missing golangci-lint binary. The localgolangci-linthook will fail once.gofiles are added. Fix: addSKIP=golangci-lintenv var to the pre-commit step (lint job covers this separately). Filed as #171..golangci-lint.yml:132–forbidigoin exclude-rules but linter not enabled. Dead config entry. Filed as #172.Praise
go.modexistence are clean — won't fail pre-emptively$FORGEJO_OUTPUTcorrectly for Forgejo Actions output passing-race -coverprofile -covermode=atomiccovers race detection and coverageRe-review: no blocking issues found across all three config files. CI pipeline is well-structured, linter selection is comprehensive, pre-commit hooks are appropriate for the project. The two suggestions filed (#171, #172) are non-blocking future-proofing items.
APPROVED