renovatebot/renovate

ci: automate removal of TODOs in codebase

Open

#41497 opened on Feb 25, 2026

View on GitHub
 (1 comment) (3 reactions) (0 assignees)TypeScript (14,066 stars) (1,916 forks)batch import
good first issuepriority-3-medium

Description

As noted in #41496, if we're closing Issues/resolving Discussions as part of PRs, we should have a CI check that catches this and makes sure that we don't forget to clean things up in the same PR.

git grep '#[0-9][0-9]*$'

Contributor guide

Tech stack
typescriptshellgithub actions
Domain
ci cd
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
GitHub Actionsshell scriptinggit commands
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Start by examining the repository's .github/workflows directory to understand the existing CI structure. The issue suggests using 'git grep' to find patterns like '#[0-9][0-9]*$' that indicate unresolved references. A simple shell script can be added to check for these patterns and fail the CI if found, ensuring that PRs clean up such references. Look at similar implementations in open source projects or consider using a pre existing tool like 'todo check'. The implementation should be integrated into the pull request workflow.