get code for PR if @claude is on PR

[allisoneer]

Important

Adds a step to checkout the PR branch in claude-comment-response.yml when a comment mentions @claude on a PR.

• Workflow Update:
  • Adds a step to claude-comment-response.yml to checkout the PR branch if the comment is on a PR.
  • Uses GitHub CLI to checkout the PR branch, handling both internal branches and forks.
• Environment:
  • Sets GH_TOKEN environment variable for authentication during checkout.
• Misc:
  • Removes an unnecessary blank line in claude-comment-response.yml.

^{This description was created by for 8e7d16f. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 8e7d16f in 1 minute and 32 seconds. Click for details.

• Reviewed 37 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 2 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .github/workflows/claude-comment-response.yml:22

• Draft comment:
  Ensure GitHub CLI is properly authenticated. The step sets GH_TOKEN, but consider adding an explicit authentication (e.g., 'gh auth login --with-token') before 'gh pr checkout' to avoid potential failures if GH CLI isn’t already authenticated.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% Setting GH_TOKEN is the correct and standard way to authenticate GitHub CLI in Actions. The workflow already sets proper permissions. Adding explicit auth steps would be redundant and non-standard. The comment shows a lack of understanding of GitHub Actions environment. Could there be edge cases where explicit auth is needed that I'm not considering? Maybe there's a reason they suggested this that I'm missing. No - in GitHub Actions, setting GH_TOKEN is the documented and standard way to authenticate. Adding explicit auth would be redundant and potentially problematic. Delete this comment. The code already handles GitHub CLI authentication correctly using standard GitHub Actions patterns.

2. .github/workflows/claude-comment-response.yml:32

• Draft comment:
  Consider removing or conditionally executing debugging outputs (e.g. echoing branch name and running 'git status') once the workflow is stable to keep logs cleaner.
• Reason this comment was not posted:
  Confidence changes required: 30% <= threshold 50% None

Workflow ID: wflow_ynccmmUhf6AFxCOR

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}