Skip to content

[v3-4-test] Show why external contributors' workflow runs wait for approval (#75832) - #75840

Merged
vatsrahul1001 merged 1 commit into
v3-4-testfrom
backport-ee62251-v3-4-test
Oct 28, 2026
Merged

vatsrahul1001 merged 1 commit into
v3-4-testfrom
backport-ee62251-v3-4-test

Conversation

@github-actions

Copy link
Copy Markdown
Contributor
  • Show why external contributors' workflow runs wait for approval

Contributors whose runs the auto-approve workflow leaves for a maintainer
only saw a label, with no reason, and a comment for each would notify
every subscriber. A pending "Workflow approval" commit status shows the
reason in the PR's checks without notifying anyone.

GitHub has no event for approving runs, but a waiting run never starts,
so a run that starts is the signal to clear the status and the label,
also for runs a maintainer approves by hand, without listing every
waiting run.

Generated-by: Claude Opus 5

  • Keep the approval status in sync with runs approved during a tick

Generated-by: Claude Opus 5

  • Re-check approved runs after the failure path writes the approval state
    (cherry picked from commit ee62251)

Co-authored-by: Jarek Potiuk jarek@potiuk.com
Generated-by: Claude Opus 5

…proval (#75832)

* Show why external contributors' workflow runs wait for approval

Contributors whose runs the auto-approve workflow leaves for a maintainer
only saw a label, with no reason, and a comment for each would notify
every subscriber. A pending "Workflow approval" commit status shows the
reason in the PR's checks without notifying anyone.

GitHub has no event for approving runs, but a waiting run never starts,
so a run that starts is the signal to clear the status and the label,
also for runs a maintainer approves by hand, without listing every
waiting run.

Generated-by: Claude Opus 5

* Keep the approval status in sync with runs approved during a tick

Generated-by: Claude Opus 5

* Re-check approved runs after the failure path writes the approval state
(cherry picked from commit ee62251)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Generated-by: Claude Opus 5
@vatsrahul1001
vatsrahul1001 force-pushed the backport-ee62251-v3-4-test branch from 5517448 to 803138b Compare October 28, 2026 08:12
@vatsrahul1001
vatsrahul1001 marked this pull request as ready for review October 28, 2026 08:12
@vatsrahul1001
vatsrahul1001 merged commit 27e709d into v3-4-test Oct 28, 2026
131 of 163 checks passed
@vatsrahul1001
vatsrahul1001 deleted the backport-ee62251-v3-4-test branch October 28, 2026 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants