feat(adr): #492 group adr check problems by file with plain messages and JSON #773
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!773
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-492-adr-check-messages"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
adr check now groups problems under their file, each as a plain what-is-wrong
plus how-to-fix sentence, ending with
adr check failed: N problems in M files.. The C1-C11 and T1 rule codes are gone from the output, the help, thereference docs, and the code; each rule has one plain name, and the
linked-issues check is now decision-issues. --json carries {file, key, problem,
fix}. With --skip-remote-issues the OK line no longer claims the forge was
checked, and the link check skips inline code spans and fenced blocks.
Closes #492
adr check now lists each MADR problem under its file, as a plain sentence that says what is wrong and how to fix it, with no rule token in the text. It ends with the line "adr check failed: N problems in M files.". The --json output carries {file, key, problem, fix} for each problem. The OK line no longer claims the forge ran when --skip-remote-issues was passed. The links rule now skips inline code spans and fenced code blocks.