Put log severity in the slog level, not an [ERROR] prefix

This commit is contained in:
Ian Gulliver
2026-09-26 17:47:55 -07:00
parent a1d454610d
commit 8fb6a2a2e5
+1 -1
View File
@@ -77,7 +77,7 @@
- `go run`, never `go build` — no binary artifacts. Use `go vet` to check compilation. `sudo go run .` when root is needed. - `go run`, never `go build` — no binary artifacts. Use `go vet` to check compilation. `sudo go run .` when root is needed.
- Install binaries to `~/bin` (`go env -w GOBIN=$HOME/bin`), not `~/.local/bin` — no hiding tools under dotfile paths. - Install binaries to `~/bin` (`go env -w GOBIN=$HOME/bin`), not `~/.local/bin` — no hiding tools under dotfile paths.
- Use literal initialization (`map[string]bool{}`) over `make()`. - Use literal initialization (`map[string]bool{}`) over `make()`.
- All-lowercase log messages. Prepend `[ERROR]` where applicable. - All-lowercase log messages. Severity goes in the log level (`slog`), never as an `[ERROR]` prefix in the message.
- Always fix gofmt without asking: any Go file you see that `gofmt -l` flags gets fixed, including lines you didn't write. This overrides "only reformat lines you touch". - Always fix gofmt without asking: any Go file you see that `gofmt -l` flags gets fixed, including lines you didn't write. This overrides "only reformat lines you touch".
# Shell # Shell