[General]: Regression baseline update workflow does not trigger pull request CI checks

[harryswift01]

Feedback or Inquiry

The manually triggered regression baseline update workflow successfully regenerates and commits updated baseline files back to the active pull request branch. However, the resulting bot-generated commit does not trigger the normal pull request CI workflows.

This occurs because the workflow currently authenticates using the default GITHUB_TOKEN, which does not trigger downstream workflow runs for security reasons.

The intended workflow is:

1. Developer opens a PR branch
2. Developer manually runs the regression baseline update workflow
3. Updated baselines are committed back to the PR branch
4. Standard PR CI workflows automatically run against the updated baselines

Potential solutions include:

• Using a fine-grained PAT for authenticated workflow commits
• Explicitly dispatching the PR workflow after baseline updates
• Alternative GitHub Actions authentication approaches that allow downstream workflow execution