feat(scorecard): expose fallback rejection visibility (#1435) - #1436
Merged
Conversation
Owner
Author
SummaryCloses #1435.
The operator decision that the fallback lane remains enabled is now reviewable through the existing ledger data. Rejection counts are visibility only and should not be interpreted as lane quality without the demand/starvation context ( Verification
|
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.
Summary
Closes #1435.
proposer_rejectrows withfallback-cycle IDs.fallback_rejects,fallback_rejects_by_reason, andfallback_distinct_target_pathsto the loop section.fallback_cycles,fallback_successes,fallback_share, andfallback_success_rateterminal-row semantics unchanged.0/{}) from an unreadable ledger (unavailable)._TARGETS; no ledger schema or fallback-lane behavior changed.The operator decision that the fallback lane remains enabled is now reviewable through the existing ledger data. Rejection counts are visibility only and should not be interpreted as lane quality without the demand/starvation context (
gaps: []).Verification
71 passed.origin/main; those seven are not caused by this PR and are documented here rather than treated as regressions.