The following are included as keys to the group.
${{ github.head_ref || github.run_id }}
This allows concurrency to work only with Push to PullRequest, and cancels all but the most recent push for successive pushes; for merge commits, in other words push events, ${{ github.run_id }} is used, so The cancellation is not enforced because it is always a unique group.
This eliminates the problem of consecutive Pushes being cancelled at the time of release.
Before submitting the PR make sure the following are checked:
[x] Feature branch is up-to-date with main (if not - rebase it).
[x] Squashed related commits together.
[-] Added tests.
[-] Updated documentation.
[-] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).
pirj
commented
1 year ago
Same as: https://github.com/rubocop/rubocop-rspec/pull/1544 https://github.com/rubocop/rubocop/pull/11414
The following are included as keys to the group.
${{ github.head_ref || github.run_id }}This allows concurrency to work only with Push to PullRequest, and cancels all but the most recent push for successive pushes; for merge commits, in other words push events,
${{ github.run_id }}is used, so The cancellation is not enforced because it is always a unique group.This eliminates the problem of consecutive Pushes being cancelled at the time of release.
Before submitting the PR make sure the following are checked:
main(if not - rebase it).CHANGELOG.mdif the new code introduces user-observable changes.bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).