The existing merge action appears for direct-merge and queue-required PRs
only after explicit successful checks and satisfied review requirements.
Accepted outcomes show distinct localized merged or queued feedback, refresh
PR state, and prevent duplicate submission; rejected requests remain retryable.
Desktop, compact, and mobile Review surfaces reuse the same mutation and
eligibility behavior with accessible, touch-usable controls.
Verification
cd apps && pnpm install --frozen-lockfile && pnpm --filter @kandev/web test -- lib/api/domains/github-api.test.ts components/github/pr-task-icon.test.ts components/github/pr-merge-button.test.tsx &&cd web && pnpm run i18n:check && pnpm run typecheck
Dependencies And Risks
Depends on Task 01's response contract.
mergeable_state=blocked is overloaded; the frontend predicate must not turn
failed protection, missing review, or changes-requested states into queue
actions.
Locale key parity is build-gated across all supported languages.
pnpm run i18n:check passed with all supported catalogs complete.
pnpm run typecheck passed.
Review remediation keeps GitHub's overloaded blocked state visually neutral
and labels the pre-submit action Merge PR; only the accepted response claims
that GitHub added the PR to its merge queue.
Queue feedback is driven by GitHub's terminal enqueued result, not
asynchronous pending acceptance.
Focused terminal-outcome coverage passes for merged, queued, rejected, and
duplicate-click paths. The full frontend suite passed 12,046 tests across
1,455 files, with four skips.
João Salavisa