fix(jira-ticket-check): skip on non-pull_request events

[pdodgen-revparts]

Summary

Adds if: github.event_name == 'pull_request' to the check-jira-ticket job so it doesn't fire on push events.

Problem

Consumer repos (e.g., encodium/manage's Pull Request Workflow) reuse this shared workflow on both pull_request and push: main triggers to share lint/test jobs. On push:main, the squash-merge commit message often doesn't carry the Jira ticket ID — semantic-conventional commits like refactor(ci): … are common and legitimate — so the check produces false-negative alerts.

Reference failing run: manage#28971802686 — merge of today's dispatch refactor PR failed the Jira check even though the PR itself was properly linked.

Fix

Skip the check on non-pull_request events. Reasoning:

• The PR-time check already validated the ticket before the merge landed.
• Running again on the resulting main push is redundant.
• Squash-merge commit format is orthogonal to whether the branch's PR had a valid ticket link.

Blast radius

Zero on the PR path — pull_request events still run the check exactly as before. Only reduces the false-negative rate on push:main.

Related

• DEVEX-1653 (RT v2 — pattern of shared workflows called from multi-trigger repo pipelines)

[cursor]

PR Summary

Low Risk
Single workflow guard with no change to PR validation behavior; only skips redundant runs on push events.

Overview
Adds if: github.event_name == 'pull_request' on the check-jira-ticket job so the shared workflow no longer runs when callers invoke it from push (e.g. push to main alongside pull_request).

That avoids false failures after squash merges, where the commit message often lacks a Jira key even though the PR already passed the check. Pull request runs are unchanged.

^{Reviewed by Cursor Bugbot for commit dc045e1. Bugbot is set up for automated code reviews on this repo. Configure here.}