Potentially but it is better than blocking the entire github action queue for hours?

We should find a better way to trigger releases than listen on check_run completed...

Perhaps have the existing GitHub workflow once all tests passes start the next job that verifies release is necessary?

Like: https://github.com/JanDeDobbeleer/oh-my-posh/blob/main/.github/workflows/release.yml

Again https://github.com/jenkinsci/configuration-as-code-plugin/actions/workflows/cd.yaml created 55 runs before even getting one release out the door.

We can also entirely remove on check_run and have it as workflow dispatch.

We can also entirely remove on check_run and have it as workflow dispatch.

That may be simplest trivial to hit the button, each action should only take 5 seconds to complete but I assume there's a queue problem that means it doesn't scale.

We could also reduce our github CI down just to running codecov?

Codecov Report

Merging #1843 (3f0ba44) into master (e8cfa34) will not change coverage.
The diff coverage is n/a.

❗ Current head 3f0ba44 differs from pull request most recent head 06fa33b. Consider uploading reports for the commit 06fa33b to get more accurate results

@@            Coverage Diff            @@
##             master    #1843   +/-   ##
=========================================
  Coverage     80.78%   80.78%           
  Complexity      838      838           
=========================================
  Files            71       71           
  Lines          2467     2467           
  Branches        346      346           
=========================================
  Hits           1993     1993           
  Misses          366      366           
  Partials        108      108