Skip to content

PROBE: resolveReviewThread token scope (do not merge) - #27

Closed
chethanuk wants to merge 2 commits into
mainfrom
probe/resolve-thread-scope
Closed

PROBE: resolveReviewThread token scope (do not merge)#27
chethanuk wants to merge 2 commits into
mainfrom
probe/resolve-thread-scope

Conversation

@chethanuk

Copy link
Copy Markdown
Owner

Throwaway probe for alibaba#567. Tests whether a GITHUB_TOKEN scoped exactly like .github/workflows/ocr-review.yml (contents: read + pull-requests: write) can execute the resolveReviewThread GraphQL mutation. Will be closed once the run reports.

@codeant-ai

codeant-ai Bot commented Aug 8, 2026

Copy link
Copy Markdown

🤖 CodeAnt AI — Review Status

Status Commit Started (UTC) Finished (UTC)
✅ Reviewed your PR 96a0a85 Aug 08, 2026 · 07:16 07:16

@codeant-ai

codeant-ai Bot commented Aug 8, 2026

Copy link
Copy Markdown

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

Comment thread probe-target.txt
@@ -0,0 +1,2 @@
probe anchor line 1

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probe: resolve-scope test comment

@coderabbitai

coderabbitai Bot commented Aug 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@chethanuk, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 56 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 797eabbf-b2bd-4c07-bb31-54d619496727

📥 Commits

Reviewing files that changed from the base of the PR and between f8f0851 and f7ea77b.

📒 Files selected for processing (2)
  • .github/workflows/probe-resolve-scope.yml
  • probe-target.txt

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codeant-ai codeant-ai Bot added the size:M This PR changes 30-99 lines, ignoring generated files label Aug 8, 2026
@codeant-ai

codeant-ai Bot commented Aug 8, 2026

Copy link
Copy Markdown

User description

Throwaway probe for alibaba#567. Tests whether a GITHUB_TOKEN scoped exactly like .github/workflows/ocr-review.yml (contents: read + pull-requests: write) can execute the resolveReviewThread GraphQL mutation. Will be closed once the run reports.


CodeAnt-AI Description

Validate pull request review-thread resolution permissions

What Changed

  • Adds a temporary workflow that runs on opened or updated pull requests
  • Posts a review comment, checks whether the workflow token can resolve its thread, and reports whether resolution succeeded or failed
  • Uses the same read and pull-request write permissions as the review workflow

Impact

✅ Verified review-thread resolution access
✅ Clear permission test results
✅ Safer review workflow configuration

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

Comment thread probe-target.txt
@chethanuk

Copy link
Copy Markdown
Owner Author

Probe complete. Result: resolveReviewThread requires contents: write; with contents: read + pull-requests: write it fails with 'Resource not accessible by integration'. Also: viewerCanResolve reported false in both runs, including the successful one, so it must not be used as a pre-flight gate.

@chethanuk chethanuk closed this Aug 8, 2026
@chethanuk
chethanuk deleted the probe/resolve-thread-scope branch August 8, 2026 07:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M This PR changes 30-99 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant