mcp: reading a repo's description/topics drops to madt_api_call; add a typed read #723
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#723
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Reading a single repo's description and topics has no obvious typed madt_* path, so I reached for the raw forge API twice: GET /repos/{owner}/{repo} for the description, and GET /repos/{owner}/{repo}/topics for the topics. Dropping to the raw API for a routine read is a smell: it is unbounded and bypasses the typed surface.
Ask
Context
madt_repos check_metadata reports repos that are MISSING metadata in aggregate, but there is no obvious per-repo read of the current values. That gap is what sent me to the raw API.