Repository navigation
Migration readiness names the refused rule in the job log - #4569
Merged
Merged
Conversation
The runner failed closed with one fixed line, so a refusal could not be told apart from a network or Git error. Our own requireFact refusals now carry a marker and print their fixed rule text; provider, Git and API errors still print nothing. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012BMmZWrkFxXJddyVkAXF4c
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
#4556 still fails migration-readiness on a head that includes #4567, and the job log only says "failed closed". A local run of the collector against #4556's base and head returns
not_applicable, so the refusal comes from something the runner sees that a local run does not (a moving PR/main read, a fetch, or the publisher).This only adds diagnostics. Our own fixed-text
requireFactrefusals carry asafemarker and printMigration readiness rule refused: <rule>. Provider, Git and API errors carry no marker and still print nothing, so no response body, token or SQL can reach the log. No rule changed.vitest scripts/migration-pr-readiness scripts/publish-migration: 114 passed.After it merges, rerunning the runner on #4556 names the rule.
Generated by Claude Code