ci: Use concurrency for pull requests only #1410

pull hebasto wants to merge 1 commits into bitcoin-core:master from hebasto:230822-concurr changing 1 files +2 −2

hebasto commented at 2:04 PM on August 22, 2023: member

This PR is an amendment for #1403.

It avoids skipping builds when some pushes were done consequentially.

From GitHub Actions docs:

When a concurrent ... workflow is queued, if another ... workflow using the same concurrency group in the repository is in progress, the queued ... workflow will be pending. Any previously pending ... workflow in the concurrency group will be canceled.

No behavior change for pull requests.

Same as https://github.com/bitcoin/bitcoin/pull/28322.

ci: Use concurrency for pull requests only

Otherwise, any previously pending workflow will be canceled on the
following push.

ee1be62d84

real-or-random added the label ci on Aug 22, 2023
real-or-random commented at 3:08 PM on August 22, 2023: contributor

Concept ACK

Have you tested that this does the right thing?
hebasto commented at 3:20 PM on August 22, 2023: member
Have you tested that this does the right thing?

Yes, I have tested these changes:
- for push events -- in my personal repo
- for pull_request events -- in the bitcoin repo (see the screenshot in https://github.com/bitcoin/bitcoin/pull/28322 description)
real-or-random approved
real-or-random commented at 9:02 AM on August 23, 2023: contributor

ACK ee1be62d84bf6d81e0ed574ef98e980d61a19227
real-or-random merged this on Aug 23, 2023
real-or-random closed this on Aug 23, 2023
real-or-random cross-referenced this on Aug 23, 2023 from issue ci: Future of CI after Cirrus pricing change by real-or-random
hebasto deleted the branch on Aug 23, 2023

Contributors

Labels