You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs(expo): give the verify skill the cloud ready route and a timed evidence wait - #10622
The wait for the evidence polls the description over REST for the table row inside the verify-evidence block, and gives up after ten minutes. gh pr ready runs only when that wait succeeds.
Docs only.
Checklist
pnpm test runs as expected.
pnpm build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
… the cloud REST forms
In a Claude Code cloud session GitHub's GraphQL API is blocked, so gh pr
create, view and ready fail. Name the REST and CCR routes that work there,
and replace the eyeballed wait with a polling check that fails after ten
minutes instead of a fixed one-minute guess.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Expo verification instructions now describe running the before check from the base-commit branch and the after check from the change branch. They poll the pull request body for the evidence table, with up to 40 attempts at 15-second intervals, before marking the pull request ready. The instructions also provide GitHub API alternatives for Claude Code cloud sessions. The changeset file contains two YAML document separators and no package release or change description.
clerk/javascript#10620: Updates the same evidence-to-ready workflow. This PR replaces its fixed wait with bounded polling and adds GitHub API commands for cloud sessions.
Merge Risk: Minimal · up to d3d7e
No actionable merge-blocking risk remains in the reviewed changes.
Pre-merge checks: 5
Check name
Status
Explanation
Title check
The title clearly summarizes the main documentation changes: adding the cloud-ready route and timed evidence polling.
Description check
The description directly explains the REST API updates, evidence polling behavior, and docs-only scope of the changeset.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
Linked repositories: Some configured repositories could not be included in this review. Cross-repository analysis may be incomplete. Please check linked-repository access and settings.
CodeRabbit Verify
Run CodeRabbit Verify to test the changes in this pull request.
Included review availability: This review used your included allowance. 2 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.
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
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.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Description
Follow-up to clerk/javascript#10620, which merged before its last two commits were pushed. Same change as clerk/clerk-ios#807 and clerk/clerk-android#1230.
gh pr create,gh pr viewandgh pr readyfail there. Theverify-clerk-exposkill now names the REST forms that work, includingPOST repos/clerk/javascript/pulls/<n>/ccr/ready_for_review. A cloud session confirmed that route by switching [BLACKSMITH TEST] fix(auth): shorten the phone field switcher label to "Use email or username" clerk-ios#805 to draft and back.verify-evidenceblock, and gives up after ten minutes.gh pr readyruns only when that wait succeeds.Docs only.
Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change
🤖 Generated with Claude Code