fix: enable E2E report comment for labeled trigger

[Kavirubc]

Fix

The E2E workflow ran successfully on PRs, but the Report Comment was skipped.
Why? The step condition checked for pull_request_review (old trigger), but we are now using pull_request_target.

Updated the condition to match pull_request_target so the bot posts the test results.

Summary by CodeRabbit

• Chores
  • Updated the GitHub Actions workflow trigger for automated PR comments to respond to pull request target events instead of pull request review events.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

A GitHub Actions workflow condition was modified to trigger the PR comment step on pull_request_target instead of pull_request_review, shifting the event that initiates the final comment posting. The workflow logic and outputs remain unchanged.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/e2e-test.yml	Modified PR-comment step condition to trigger on pull_request_target event instead of pull_request_review event.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• fix: run E2E only when review is approved (secure for forks) #78: Modifies the same e2e-test workflow triggers and PR-comment step behavior, including event trigger conditions and authentication handling.

Suggested labels

bug, ci/cd

Suggested reviewers

• gh-simili-bot

Poem

🐰 A workflow leaps to a different beat,
From review to target, the timing's neat!
The comment still sings with the same cheer,
Just when it posts—ah, a shift appears!
Carrots for CI/CD, hooray! 🥕✨

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/e2e-report-trigger

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gh-simili-bot]

Simili Triage Report

Note

Quality Score: 8.5/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category	Value
Labels

Quality Improvements

• Missing direct link to a workflow run demonstrating the skipped comment
• Provide a link to a specific GitHub Actions workflow run where the report comment was observed to be skipped.

Similar Threads

Similarity	Thread	Status
85%	#79 fix: use 'e2e' label trigger for secure secrets...	Open
79%	#74 fix: prevent bot loop & enable E2E for forks	Closed
78%	#78 fix: run E2E only when review is approved (secu...	Open

---

_{Generated by Simili Bot}