-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Sweep low-risk comment typos and stale wording in cleanup TODOs #18226
Copy link
Copy link
Open
Labels
cleanupCode cleanup or removal of dead codeCode cleanup or removal of dead codecode-styleRelated to code formatting or style conventionsRelated to code formatting or style conventionsgood first issueGood for newcomers — GitHub surfaces this in the Contribute tabGood for newcomers — GitHub surfaces this in the Contribute tabjavaPull requests that update Java codePull requests that update Java codeminorSmall or trivial changeSmall or trivial changepriority: lowNice to have, can waitNice to have, can wait
Description
Metadata
Metadata
Assignees
Labels
cleanupCode cleanup or removal of dead codeCode cleanup or removal of dead codecode-styleRelated to code formatting or style conventionsRelated to code formatting or style conventionsgood first issueGood for newcomers — GitHub surfaces this in the Contribute tabGood for newcomers — GitHub surfaces this in the Contribute tabjavaPull requests that update Java codePull requests that update Java codeminorSmall or trivial changeSmall or trivial changepriority: lowNice to have, can waitNice to have, can wait
Type
Fields
Give feedbackNo fields configured for issues without a type.
Motivation
There are still trivial comment-level cleanup items, for example
pinot-plugins/pinot-minion-tasks/pinot-minion-builtin-tasks/src/main/java/org/apache/pinot/plugin/minion/tasks/refreshsegment/RefreshSegmentTaskExecutor.javasayssupproted.Other TODO and FIXME comments in the same low-hanging-fruit bucket also look stale or under-specified. These are small issues, but they create noise and make it harder to tell which comments still carry actionable engineering debt.
Scope
Notes
Observed on
upstream/masteron April 15, 2026.