fix: automerge workflow event condition

[JohnMcLear]

Summary

• The automerge workflow checks github.event.workflow_run.event == 'pull_request', but the Node.js Package workflow triggers on push events
• This means the automerge condition is never satisfied and dependabot PRs are never auto-merged
• Fix: change the condition to check for push instead of pull_request

Test plan

• Verify automerge workflow runs are no longer skipped when dependabot PRs pass CI

Generated with Claude Code

[qodo-free-for-open-source-projects]

Review Summary by Qodo

Fix automerge workflow event condition for dependabot

🐞 Bug fix

Walkthroughs

Description

• Fix automerge workflow event condition from pull_request to push
• Aligns condition with actual Node.js Package workflow trigger event
• Enables dependabot PRs to be auto-merged when CI passes

Diagram

flowchart LR
  A["Automerge Workflow"] -->|checks event type| B["Event Condition"]
  B -->|was checking| C["pull_request"]
  B -->|now checks| D["push"]
  D -->|matches| E["Node.js Package Workflow trigger"]

Loading

File Changes

1. .github/workflows/automerge.yml 🐞 Bug fix +1/-1

Update automerge event condition to push

• Changed workflow event condition from pull_request to push
• Fixes mismatch between automerge trigger condition and actual Node.js Package workflow event type
• Allows dependabot PRs to be auto-merged when CI passes successfully

.github/workflows/automerge.yml

---

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (1)   📘 Rule violations (0)   📎 Requirement gaps (0)

🐞\ ≡ Correctness (1)

1. Automerge event filter wrong 🐞 ≡

Description

Dependabot Automerge now requires github.event.workflow_run.event == 'push', but it is triggered
by completed runs of the CI workflow which runs on pull_request; this will skip successful
Dependabot PR CI runs. This prevents the automerge job from running in the scenario it’s meant to
handle (Dependabot PRs passing CI).

Code

.github/workflows/automerge.yml[R14-17]

    if: >
      github.event.workflow_run.conclusion == 'success' &&
-      github.event.workflow_run.event == 'pull_request' &&
+      github.event.workflow_run.event == 'push' &&
      github.event.workflow_run.actor.login == 'dependabot[bot]'

Evidence

The automerge workflow listens to workflow_run events for workflow CI. The CI workflow is
explicitly triggered on pull_request, so for a PR CI run the workflow_run.event value will be
pull_request. Changing the automerge predicate to require push therefore filters out the CI runs
created for PRs (including Dependabot PRs), so the automerge job won’t execute after PR CI success.

.github/workflows/automerge.yml[5-17]
.github/workflows/ci.yml[1-7]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`automerge.yml` filters `workflow_run` events to `event == 'push'`, but the monitored workflow (`CI`) runs for `pull_request` events as well. This prevents the automerge job from running after successful PR CI runs.

### Issue Context
`Dependabot Automerge` is triggered by `workflow_run` of the `CI` workflow. Since `CI` runs on `pull_request`, the automerge workflow must allow `workflow_run.event == 'pull_request'` (or allow both `pull_request` and `push` if you intentionally want both).

### Fix Focus Areas
- .github/workflows/automerge.yml[14-17]

### Concrete fix
Update the `if:` condition to match the intended trigger, e.g.:
- Revert to `github.event.workflow_run.event == 'pull_request'`, **or**
- Allow both: `contains(fromJson('["pull_request","push"]'), github.event.workflow_run.event)` (only if you truly want automerge to run for both kinds of CI runs).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[qodo-free-for-open-source-projects]

1. Automerge event filter wrong 🐞 Bug ≡ Correctness

Dependabot Automerge now requires github.event.workflow_run.event == 'push', but it is triggered
by completed runs of the CI workflow which runs on pull_request; this will skip successful
Dependabot PR CI runs. This prevents the automerge job from running in the scenario it’s meant to
handle (Dependabot PRs passing CI).

Agent Prompt

### Issue description
`automerge.yml` filters `workflow_run` events to `event == 'push'`, but the monitored workflow (`CI`) runs for `pull_request` events as well. This prevents the automerge job from running after successful PR CI runs.

### Issue Context
`Dependabot Automerge` is triggered by `workflow_run` of the `CI` workflow. Since `CI` runs on `pull_request`, the automerge workflow must allow `workflow_run.event == 'pull_request'` (or allow both `pull_request` and `push` if you intentionally want both).

### Fix Focus Areas
- .github/workflows/automerge.yml[14-17]

### Concrete fix
Update the `if:` condition to match the intended trigger, e.g.:
- Revert to `github.event.workflow_run.event == 'pull_request'`, **or**
- Allow both: `contains(fromJson('["pull_request","push"]'), github.event.workflow_run.event)` (only if you truly want automerge to run for both kinds of CI runs).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools