velero-io/velero

Enable context TODO Linter

Open

#10,086 opened on Jul 27, 2026

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Go (1,550 forks)auto 404
Enhancement/UserGood first issueNeeds triagekind/tech-debt

Repository metrics

Stars
 (10,111 stars)
PR merge metrics
 (PR metrics pending)

Description

There's a lot of context TODO prior to this pr that in future pr we should eliminate for proper cancellations handling. Not for this pr. I think there's Linter setting for this. Exception for test code.

Originally posted by @kaovilai in #9697

Contributor guide

Research direction
Look at the existing linter configuration (likely .golangci.yml) in the repository. Enable a linter that flags context.TODO() calls, such as 'contextcheck', and configure it to ignore test files. Check the linked PR #9697 for discussion context and any related changes.
Tech stack
go
Domain
backendtooling
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75