CI: enforce regexpcompileinfunction and fprintlnsprintf in custom linter gate

[Copilot]

Sergo R22 identified two registered custom analyzers that were not included in CI’s enforced LINTER_FLAGS, despite having zero production diagnostics. This PR aligns CI enforcement with the analyzer set already maintained in cmd/linters/main.go to prevent future regressions.

• What changed

  • Updated .github/workflows/cgo.yml (Run custom linters) to include:
    • -regexpcompileinfunction
    • -fprintlnsprintf

• Impact

  • CI now fails on newly introduced:
    • in-function compile-time-constant regex compilation
    • fmt.Fprintln(w, fmt.Sprintf(...)) patterns
  • Existing analyzer coverage remains unchanged; this extends the explicit enforced set.

• Workflow diff

  - run: make golint-custom LINTER_FLAGS="-errstringmatch -panicinlibrarycode -manualmutexunlock -osexitinlibrary -rawloginlib -test=false"
  + run: make golint-custom LINTER_FLAGS="-errstringmatch -panicinlibrarycode -manualmutexunlock -osexitinlibrary -rawloginlib -regexpcompileinfunction -fprintlnsprintf -test=false"

[Copilot]

Pull request overview

Updates CI’s custom-linter gate to explicitly enforce two already-registered custom Go analyzers (regexpcompileinfunction and fprintlnsprintf), aligning the workflow with the analyzer set maintained in cmd/linters/main.go.

Changes:

• Extend the make golint-custom LINTER_FLAGS in .github/workflows/cgo.yml to include -regexpcompileinfunction.
• Extend the same enforced set to include -fprintlnsprintf.

Show a summary per file

File	Description
.github/workflows/cgo.yml	Adds two custom analyzer flags to the CI “Run custom linters” step so the CI gate matches the maintained analyzer set.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 0