Skip to content

[deep-report] Introduce sentinel errors for recurring string matches (remove errstringmatch nolint suppressions) #46264

Description

@github-actions

Description

The [repository-quality] report (discussion #46253) found gh-aw has a mature error story (15 named error types, 121 errors.Is/errors.As callsites) yet only 4 var ErrXxx = errors.New sentinels and 4 strings.Contains(err.Error(), ...) matches in production. Promote the most-rematched error strings (e.g. in schedule_preprocessing.go and update_extension_check.go) to typed sentinel errors so callers use errors.Is instead of brittle substring matching, eliminating the associated (nolint/redacted):errstringmatch suppressions.

Expected Impact

Robust, refactor-proof error classification; removes 2 lint suppressions; makes error-cause inspection reliable rather than string-fragile.

Suggested Agent

Copilot SWE Agent (top performer this week, 92/100 quality; handles Go refactors).

Estimated Effort

Quick (< 1 hour) — Small, self-contained per the report.

Data Source

DeepReport 2026-07-17 analysis - [repository-quality] discussion #46253 Task 1/Task 5. Dedup-checked: no open issue covers sentinel-error promotion.

Generated by 🔬 Deep Report · 208.7 AIC · ⌖ 11.4 AIC · ⊞ 10K ·

  • expires on Jul 19, 2026, 7:16 AM UTC-08:00

Metadata

Metadata

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions