ci: Replace pull_request_target with pull_request in GitHub Actions

[baillyjamy]

Description

Replace pull_request_target with pull_request in GitHub Actions workflows.

Why

pull_request_target runs in the context of the base branch with full access to repository secrets, even for fork PRs. This is unnecessary and a potential security risk for workflows that only need read access (semantic commit check, dependent issues, auto-author assign).

Since all PRs come from within the organization, pull_request is sufficient.

Changes

• .github/workflows/dependent-issues.yml: pull_request_target → pull_request
• .github/workflows/auto-author-assign.yml: pull_request_target → pull_request
• .github/workflows/semantic-commit.yml (if present): pull_request_target → pull_request

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

This PR hardens GitHub Actions execution for PR-related workflows by switching from pull_request_target (base-branch context with broader secret exposure) to pull_request, and adds job-level guards to avoid running write-capable jobs on forked PRs.

Changes:

• Updated workflows to trigger on pull_request instead of pull_request_target.
• Added job-level if: conditions to only execute on same-repo PRs (and still run for issues events where applicable).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.github/workflows/dependent-issues.yml	Switches to pull_request and adds a job if: guard to skip fork PRs while still running on issues events.
.github/workflows/auto-author-assign.yml	Switches to pull_request and adds a job if: guard to skip fork PRs (where write permissions wouldn’t be available).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.