Skip to content

Migration readiness names the error class and stage for non-rule failures - #4574

Merged
hellofrequencylab merged 1 commit into
mainfrom
claude/migration-readiness-stage
Nov 3, 2026
Merged

hellofrequencylab merged 1 commit into
mainfrom
claude/migration-readiness-stage

Conversation

@hellofrequencylab

Copy link
Copy Markdown
Owner

#4569 made our own fixed-text refusals visible, but #4556's failure still prints only the generic line, so it is not one of our refusals. It is a Git or API error thrown inside the collector.

This prints only the error class, code, exit status and a fixed stage label (git-<subcommand> or github-api) for those errors. Messages, stderr, command arguments and provider bodies stay out of the log. No rule changed. vitest scripts/migration-pr-readiness scripts/publish-migration: 114 passed.

After it merges, an update of #4556 shows which step fails (fetch, show, diff, or an API read).


Generated by Claude Code

…ures

The rule names from the last change never appeared for #4556, so its failure is a
Git or API error, not one of our own refusals. The log now prints only the error
class, code, exit status and a fixed stage label (git-<subcommand> or github-api).
Messages, stderr, command arguments and provider bodies stay out of the log.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012BMmZWrkFxXJddyVkAXF4c
@vercel

vercel Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
frequency-web Ready Ready Preview Nov 3, 2026 7:48pm UTC

Request Review

This branch was successfully deployed

1 active deployment
Preview — 69953f20 Deployed Nov 3, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants