ci: Use concurrency for pull requests only #1410

1. 
   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.

2. ci: Use concurrency for pull requests only

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

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

   Concept ACK

   Have you tested that this does the right thing?

5. 
   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)
6. real-or-random approved
7. 
   real-or-random commented at 9:02 am on August 23, 2023: contributor

   ACK ee1be62d84bf6d81e0ed574ef98e980d61a19227
8. real-or-random merged this on Aug 23, 2023
9. real-or-random closed this on Aug 23, 2023

   ---

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

Contributors
hebasto real-or-random

Labels
ci