Repository navigation
docs(quality): link the dicompare unused-code findings to dicompare-web#32 - #558
Merged
Merged
Conversation
…eb#32 Refs #557 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 2026-10-22 unused-code triage record still said no upstream issue tracks the six dicompare findings. They are now tracked in astewartau/dicompare-web#32. This changes that row to link the issue, as the QSMbly row links astewartau/qsmbly#157.
This is a documentation change only. Codex review found no issues.
Refs #557. The issue's second item stays open: record that the findings are gone once the weekly sync brings in the upstream fixes.
🤖 Generated with Claude Code