Exclude goconst linter from test files

[gontzess]

Why

Test files naturally repeat string literals ("user", "group", "expected", etc.) across test cases. Extracting these into constants hurts test readability without meaningful safety benefit. This is standard Go community practice.

What this changes

Adds an exclusion rule to .golangci.yml that skips goconst checks in *_test.go files:

exclusions:
  rules:
    - path: _test\.go$
      linters:
        - goconst

This affects all repos that use this config via the verify workflow.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• .golangci.yml is excluded by none and included by none

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ce6ed5e8-7e9f-4e7c-8a87-5c78a39500b3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch gontzess/exclude-goconst-from-tests

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[johnallers]

Not sure how others feel, but it seems reasonable to me.