Eligible pull_request events do not create the GitHub Actions workflow run

[MDPAuto]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Configuration

Discussion Details

We are seeing a reproducible GitHub Actions workflow-trigger failure in a private repository.

Repository: MDPAuto/mdp-crm-dms
Workflow: Validate
Workflow path: .github/workflows/ci.yml
Workflow ID: 313310722
Target branch: main
Head SHA: a6214ba8f19a063490d81734d006d3d392c49adf

The workflow trigger is:

name: Validate

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

EXPECTED BEHAVIOUR

Opening, synchronizing or reopening a non-draft, mergeable pull request targeting main should create a Validate workflow run.

ACTUAL BEHAVIOUR

No Validate workflow run was created.

There is also:

• no skipped Validate run;
• no approval-required Validate run;
• no pending Validate check;
• no workflow run available to rerun.

This occurred for two separate pull requests pointing to the same reviewed commit:

• PR #165
• PR #166

PR #166 was created manually by the repository owner through the GitHub web interface from a newly created branch.

Both pull requests:

• target main;
• are open and mergeable;
• are not drafts;
• contain no CI skip annotations;
• contain the same four approved application files;
• use a workflow file identical to the version on main.

For PR #165, all these eligible events failed to create a Validate run:

• opened;
• multiple synchronize events;
• a manually generated reopened event.

For PR #166, the manually generated opened event also failed to create a Validate run.

GITHUB ACTIONS IS OTHERWISE OPERATIONAL

• The Validate workflow is enabled.
• Validate run #586 completed successfully for PR #164.
• Validate run #587 completed successfully for the PR #164 merge commit on main.
• Other recent workflow runs are created and receive GitHub-hosted runners.
• Repository Actions permissions allow all actions and reusable workflows.
• The GitHub Actions budget is available and not exhausted.
• External integrations such as Netlify and Supabase are created normally.

WORKFLOW RESTRICTIONS CHECKED

The workflow has:

• no pull_request activity-type restriction;
• no paths or paths-ignore filters;
• no source-branch restriction;
• no workflow-level if condition;
• no workflow-level concurrency restriction;
• no workflow_dispatch trigger.

The current head commit contains no skip-ci, skip-actions or skip-checks instruction.

We have deliberately not:

• added a no-op commit;
• changed the workflow merely to force execution;
• weakened required checks;
• merged either pull request;
• deployed the application.

Could someone advise how to determine why GitHub is not creating a workflow run for these eligible pull_request events?

If GitHub staff need to inspect backend workflow-event admission, please advise the correct escalation route for a GitHub Free account.

Supporting screenshots

PR #165 — Checks page

PR #166 — Checks page

Repository Actions page

Actions permissions

Actions budget

PR #165 — event timeline

PR #166 — manually created replacement PR

Validate workflow definition

ci.yml.txt

[binh-dev-k2]

Looks like it's a GitHub Actions incident, not your workflow. https://www.githubstatus.com/