Fix #518: zero-checks empty state #524
No reviewers
Labels
No labels
actions
bug
cli
duplicate
enhancement
fork
forum
git storage
help wanted
insights
invalid
issues
moderation
oidc
ownership transfer
packages
pr/merge protection rules
projects
pull requests
question
releases
sponsorships
tags
webhooks
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
crueber/walhub!524
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/issue-518"
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?
Client display only — NO wire change (combinedState zero⇒pending stays for the gate).\n\n- New pure
web/src/lib/checks-empty.js:isZeroChecks(empty = zero-length statuses array; a single pending context is still in-flight),zeroChecksTitle(No checks configured iff required is known-empty, else No checks reported yet),requiredCheckBlockers(Pull.jsx logic moved verbatim, incl.<ctx> (missing)).\n-CheckPillrenders a neutral zinc no-checks pill on zero; real combined pill otherwise (commit pages unaffected for non-empty).\n- PR checks card swapsContextRowsforZeroChecksBlockon zero (required-aware title + waiting-on-required line); required/blocking-merge lines and merge-button tooltip unchanged.\n-CheckDetailsame treatment, sharing the CheckPill data key (no extra request).\n- Reporting guidance reuses existing surfaces only: POST …/checks/statuses/{sha} + wct_ token, links to /api#checks-ci and the checks page.\n- Law-12 decision appended to docs/features/05_checks_statuses.md.\n\nTests: new web/test/unit/checks-empty-518.test.js (8 tests: empty-vs-pending distinction, titles, blockers incl. (missing), src wiring pins); 28/28 across checks-empty-518 + sdk-checks + checks-tab-505/513 + pull-state-517; full web suite 1169/1170 (sole failure = smoke /setup 403 vs live :8080 instance, pre-existing on main, environmental); vite build clean. No backend change, no new deps. No browser drive (shared daemon blocks loopback per task note); mobile-viewport check still owed on review.