[uniqueg]

Summary

Only a new head commit of a pull request now cancels its CI runs in progress: cancel-in-progress of the workflow-level concurrency block in .github/workflows/ci.yml is true only for pull_request with action synchronize on the first attempt, as in "Cancelled runs" of actions/gate/README.md in elixir-cloud-aai/.github (elixir-cloud-aai/.github#71):

cancel-in-progress: >-
  ${{ github.event_name == 'pull_request'
  && github.event.action == 'synchronize'
  && github.run_attempt == 1 }}

Before, a newer run on the same commit (e.g. for editing the description, also by Sourcery, or marking the pull request ready) cancelled the run in progress, and its failed CI passed was then the newest result on the commit, which blocked the merge (elixir-cloud-aai/.github#70). Runs for other actions, and reruns, now wait for the run in progress instead; a waiting run that is replaced starts no job, so it leaves no check. The gate keeps if: always(), so a needed job that failed or was cancelled still fails it. This pull request's own runs already use the new rule.

The concurrency groups are unchanged (runs for pushes and for edits that leave the title unchanged keep groups of their own); the comment above the block now describes the new rule.

tests/test_workflows.py gets test_ci_concurrency, which asserts the new expression and the whole group expression, in which runs for pushes have a group of their own (written first; it failed before the change).

Part of elixir-cloud-aai/.github#73

Verification

• pre-commit run --files on .github/workflows/ci.yml and the test file (all hooks of the repository): passed.
• pytest tests/test_workflows.py -k concurrency: failed before the change, passes after it.
• pytest -W ignore::DeprecationWarning: 1617 passed, 11 skipped, 188 failed, all in tests/test_chart.py (186) and tests/test_config_examples.py::test_chart_examples_valid (2): the chart tests (tests/test_chart.py, and the chart examples in tests/test_config_examples.py) could not run locally, as Helm isn't installed here; CI runs them.
• CI: all checks passed, including CI passed, on 3be015e.
• Sourcery: 1 thread (the test checked the push part of the group as a substring): fixed in 3be015e, the test asserts the whole group expression; resolved.

Light lane: changes only the CI workflow's concurrency settings and a test of them (no secrets, permissions or release workflow); I reviewed the diff myself.

Declined review findings

None.

Open questions

None.

🤖 Generated with Claude Code

https://claude.ai/code/session_011FSoqMpmDCfbACLj3uy6xV

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (55c4d15) to head (3be015e).

Additional details and impacted files

@@            Coverage Diff            @@
##               dev      #473   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           31        31           
  Lines         3007      3007           
=========================================
  Hits          3007      3007           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sourcery-ai]

Reviewer's Guide

Configuration

Restrict workflow cancellation to first-attempt pull-request synchronize runs while documenting the rule and preserving the existing concurrency groups.

• .github/workflows/ci.yml L39-46, L54-57

Tests

Assert the cancellation condition and the complete concurrency-group expression, including the separate push grouping.

• tests/test_workflows.py L76-102

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="tests/test_workflows.py" line_range="94" />
<code_context>
+        " && github.run_attempt == 1 }}"
+    )
+    group = " ".join(concurrency["group"].split())
+    assert "github.event_name == 'push' && github.sha ||" in group
+
+
</code_context>
<issue_to_address>
**Push runs can be dropped**

When the workflow group expression is prefixed with `false &&`, `test_ci_concurrency` line 94 only checks that the group contains the push-and-SHA substring. Prefixing the expression with `false &&` makes it use the fallback group for pushes, so successive pushes can replace queued runs, yet the assertion still passes.

Assert that the group expression uses the push-and-SHA branch as its active first alternative, rather than checking only for a substring.
</issue_to_address>

Sourcery assessment

Approval pending. 1 finding to address first.

Blocking findings: tests/test_workflows.py:94

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[sourcery-ai]

Sourcery assessment

Approved.