Skip to content

Commit 54f645d

Browse files
authored
Check for workflow runs to auto-approve every 15 minutes (#75655)
External contributors' runs wait for the next approver pass before they start, and GitHub regularly drops scheduled runs under load, which turns the 30-minute wait into an hour or more. A pass takes about a minute, so running it twice as often costs little and halves the wait. Generated-by: Claude Opus 5
1 parent bb213a3 commit 54f645d

5 files changed

Lines changed: 5 additions & 5 deletions

File tree

‎.github/workflows/auto-approve-workflow-runs.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@
2929
name: Auto approve workflow runs
3030
on: # yamllint disable-line rule:truthy
3131
schedule:
32-
- cron: '*/30 * * * *'
32+
- cron: '*/15 * * * *'
3333
workflow_dispatch:
3434
inputs:
3535
report-only:

‎contributing-docs/05_pull_requests.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -247,7 +247,7 @@ CI workflow runs of external contributors
247247

248248
GitHub does not start the CI workflows of a PR from a fork until a maintainer approves them,
249249
for the contributors that the repository's approval setting covers. To keep you from waiting
250-
for a maintainer on every push, a scheduled workflow checks the waiting runs every 30 minutes
250+
for a maintainer on every push, a scheduled workflow checks the waiting runs every 15 minutes
251251
and approves them automatically when all of these hold:
252252

253253
* The PR targets ``main``. PRs to release branches, such as ``v3-4-test``, always wait for a

‎dev/breeze/doc/08_ci_tasks.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -203,7 +203,7 @@ These are all available flags of ``fork-ci-reconcile`` command:
203203
Approving workflow runs of external contributors
204204
------------------------------------------------
205205

206-
The ``auto-approve-workflow-runs`` workflow runs ``approve-workflow-runs`` every 30 minutes. It approves
206+
The ``auto-approve-workflow-runs`` workflow runs ``approve-workflow-runs`` every 15 minutes. It approves
207207
the waiting workflow runs of external contributors' PRs to ``main`` whose CI jobs are estimated at no more
208208
than 310 job-minutes, that change at most 100 lines of source code and that do not touch CI definition files, and labels the other PRs ``need workflow approval``. PRs whose CI runs in
209209
the contributor's fork (AIP-120) only run the fork CI gate in ``apache/airflow``, so their runs are

‎dev/breeze/doc/ci/05_workflows.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ everything after it, so the run finishes in seconds; see
102102

103103
GitHub holds the runs of a fork PR in `action_required` until someone with write access approves
104104
them, for the contributors the repository's approval setting covers. The
105-
`auto-approve-workflow-runs.yml` workflow runs every 30 minutes on `main` and calls
105+
`auto-approve-workflow-runs.yml` workflow runs every 15 minutes on `main` and calls
106106
`breeze ci approve-workflow-runs`, which approves the waiting runs of a commit when all of these hold:
107107

108108
- the PR targets `main`; PRs to release branches (`v3-4-test`, `airflow-ctl/v0-1-test`, ...) run those

‎dev/breeze/doc/ci/08_fork_ci_for_external_contributors.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -347,7 +347,7 @@ then the gate job does not run either. A gated pull request would stay in the ma
347347
queue even though its project CI run only executes the gate, and the reconciler could not delete a
348348
gated run that never ran.
349349

350-
`breeze ci approve-workflow-runs`, run every 30 minutes by `auto-approve-workflow-runs.yml` (see
350+
`breeze ci approve-workflow-runs`, run every 15 minutes by `auto-approve-workflow-runs.yml` (see
351351
[CI workflows](05_workflows.md#approval-of-pull-request-runs)), handles them. For a pull request to
352352
`main` it calls `fork_ci_gate.decide` with the configuration of its own `main` checkout and the
353353
pull request's author, association, creation time, head repository and current labels, the inputs

0 commit comments

Comments
 (0)