[wp-trac] [WordPress Trac] #53080: Use the `concurrency` option in GitHub Actions workflows.

[WordPress Trac]

#53080: Use the `concurrency` option in GitHub Actions workflows.
------------------------------+----------------------------
 Reporter:  desrosj           |      Owner:  (none)
     Type:  defect (bug)      |     Status:  new
 Priority:  normal            |  Milestone:  Future Release
Component:  Build/Test Tools  |    Version:
 Severity:  normal            |   Keywords:
  Focuses:                    |
------------------------------+----------------------------
 GitHub has recently announced a new `concurrency` key for use at the
 workflow and job level to ensure only a single workflow run or job is in
 progress. When used in combination with the `cancel-in-progress` key,
 incomplete workflow runs can be cancelled automatically to prevent running
 workflows unnecessarily.

 The feature is currently in beta. However, once it's stable enough, this
 can replace the need to rely on the 3rd party `styfle/cancel-workflow-
 action` action.

 Related information:
 - [https://github.blog/changelog/2021-04-19-github-actions-limit-workflow-
 run-or-job-concurrency/ Announcement post]
 - [https://docs.github.com/en/actions/reference/workflow-syntax-for-
 github-actions#concurrency Updated GitHub Actions documentation]
 - https://github.com/styfle/cancel-workflow-action/issues/76

 Some outstanding bug reports:
 - https://github.community/t/concurrency-cancel-in-progress-at-top-level-
 doesnt-seem-to-cancel-running-workflows/175801
 - https://github.community/t/actions-concurrency-bug-report/175695

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53080>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform