fix(workflow): use pull_request_target for PR triage

[Harxhit]

Summary

Switches the pull request triage workflow from pull_request to pull_request_target to ensure the workflow has the required permissions to apply labels and post comments on pull requests.

During testing, workflow logs showed that the GITHUB_TOKEN was being granted read-only permissions, causing label and comment operations to fail with 403 Resource not accessible by integration. Using pull_request_target resolves this by running the workflow with the permissions of the target repository.

---

What Changed

• Updated the PR triage workflow trigger from pull_request to pull_request_target.
• Fixed permission issues preventing automatic labeling and reviewer notification.
• Verified the workflow can access the required write permissions for PR triage actions.

---

[vercel]

@Harxhit is attempting to deploy a commit to the Prashantkumar Khatri's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

CI — All Checks Passed

Backend — SKIP

Check	Result
Lint	-
Test	-
Typecheck	-

Mobile — SKIP

Check	Result
Lint	-
Test	-

Web — SKIP

Check	Result
Check	-
Build	-

---

Last updated: Tue, 09 Jun 2026 08:11:31 GMT

[Harxhit]

@ShantKhatri Please review when you get a chance. I switched the workflow to pull_request_target to fix the permission issues we hit during testing.