Skip to content

Commit 0fa1d8b

Browse files
jdaltonjdalton
committed
ci: trigger on push, never pull_request
The fleet takes no outside contributions and lands on main directly, so a pull_request trigger adds no coverage a push trigger does not already give. It is also the fragile half: GitHub has narrowed pull_request defaults for security, and a silently non-firing trigger reads as a green repo with no CI at all — sdxgen's PR 121 created no run at all today despite a clean mergeable state. The push trigger already covers main and tags, so dropping the pull_request half leaves the same commits verified.
1 parent 0f781c5 commit 0fa1d8b

1 file changed

Lines changed: 5 additions & 2 deletions

File tree

‎.github/workflows/ci.yml‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,12 +7,15 @@
77
# top-level `jobs:` key). See scripts/repo/sync-scaffolding/checks/workflow-fleet-block.mts.
88
name: ⚡ CI
99

10+
# PUSH, never pull_request. The fleet takes no outside contributions and
11+
# lands on main directly, so a pull_request trigger adds no coverage a push
12+
# trigger does not already give — and it is the fragile half: GitHub has
13+
# narrowed pull_request defaults for security, and a silently non-firing
14+
# trigger reads as a green repo with no CI at all.
1015
on:
1116
push:
1217
branches: [main]
1318
tags: ['*']
14-
pull_request:
15-
branches: [main]
1619
workflow_dispatch:
1720

1821
permissions:

0 commit comments

Comments
 (0)