Repository navigation
evetest ci: resolve the PR in lf-edge/eve, not the fork - #7003
Merged
Merged
Conversation
For PRs from forks, evetest-pr checks out the PR's head repository, so the git remote in the workspace points at the fork. Without GH_REPO, gh infers the repository from that remote, and both `gh pr comment` (posting Claude's failure analysis) and `gh pr diff` (in live-investigation-watcher.sh) look up the PR number in the fork and fail with "Could not resolve to a PullRequest". The analysis comment step has continue-on-error, so it failed silently and no analysis was posted; the watcher likewise ran Claude without the PR diff. Set GH_REPO to github.repository for both steps, as the step that collapses previous analysis comments already does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Milan Lenco <milan@zededa.com>
milan-zededa
requested review from
eriknordmark,
rene,
shjala and
yash-zededa
as code owners
November 1, 2026 18:35
rene
approved these changes
Nov 2, 2026
Merged
6 of 9 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
For PRs from forks,
evetest-prchecks out the PR's head repository, so thegit remote in the runner workspace points at the fork. Without
GH_REPO,ghinfers the repository from that remote, and both of these look up the PR number
in the fork instead of
lf-edge/eve:gh pr commentin the "Post Claude's analysis as a PR comment" step, whichfails with
GraphQL: Could not resolve to a PullRequest with the number of N.The step has
continue-on-error: true, so it fails silently and no analysiscomment is posted (seen on 2-Node HA, part 1: witness as the third etcd voting member #6933, run 41236995199).
gh pr diffinlive-investigation-watcher.sh, which logscould not fetch the diff for PR #N, so Claude investigates failures withoutthe PR diff and can't judge whether the PR caused them.
This PR sets
GH_REPO: ${{ github.repository }}for both steps, as the step thatcollapses previous analysis comments already does.
How to test and validate this PR
On a PR opened from a fork with a failing evetest suite, run
/evetest. Thencheck that:
fetched the diff for PR #Ninsteadof
could not fetch the diff for PR #N;a
<suite>: failure analysiscomment.Changelog notes
None (CI tooling only).
PR Backports
Not to be backported standalone. The evetest workflow files will be backported
as a whole once they work correctly.
Checklist
check them.
🤖 Generated with Claude Code