🐛 Bug - PR deployment workflow is incorrectly triggered by issue comments

[ssw-yakshaver]

Requested by: @wicksipedia via YakShaver.ai 🦬
cc: @wicksipedia, @joshbermanssw, @Marxoz, @PothieuG, @Freego1783

Hi Team!

  🟥  Watch the video (2 min 43 sec)

  Url from screen share: https://github.com

Pain

A GitHub Actions workflow intended to deploy pull requests to the staging slot is being triggered when a user comments on a GitHub issue. This results in skipped or attempted PR deployments that are incorrectly attributed to the commenter, even though no pull request exists or was interacted with. The workflow behavior does not match its name, description, or expected trigger conditions, causing confusion during production incident investigation and unnecessary action log noise. This behavior has been occurring for at least the past month.

Acceptance Criteria

1. The PR deployment workflow is only triggered by valid pull request–related events (e.g., pull request creation, update, or explicit PR comments).
2. Commenting on a GitHub issue does not trigger any PR deployment workflows.
3. Workflow names, descriptions, and trigger conditions accurately reflect their actual behavior.
4. No skipped or failed PR deployment actions appear in the action log as a result of issue comments.
5. Documentation or inline comments in the workflow file clearly explain the intended trigger behavior.

Reproduce Steps

1. Navigate to the Rules V3 (TinaCMS) GitHub repository.
2. Open an existing GitHub issue (not a pull request).
3. Post a comment on the issue.
4. Go to the GitHub Actions tab and review recent workflow runs.
5. Observe that the 'Deploy Pull Request to Staging' workflow is triggered or skipped despite no pull request interaction.

Screenshot

Figure: Issue comments triggering pull request deployments