cancel overlapping gh actions runs

[achristmascarl]

Important

Add concurrency configuration to cancel in-progress GitHub Actions runs for the same pull request in ci.yml.

• Concurrency:
  • Adds concurrency configuration to .github/workflows/ci.yml to cancel in-progress runs for the same pull request using group: ci-${{ github.event.pull_request.number || github.ref }} and cancel-in-progress: true.

^{This description was created by for b3790d5. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to b3790d5 in 1 minute and 37 seconds. Click for details.

• Reviewed 17 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .github/workflows/ci.yml:9

• Draft comment:
  The new concurrency block is correctly placed to cancel overlapping runs. Consider including a unique identifier (e.g. github.workflow) in the group name so that runs from different workflows don’t conflict. Also, verify that using github.ref (which might include slashes) won’t cause issues with the concurrency group naming.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 50% <= threshold 50% The comment suggests a specific improvement by including a unique identifier in the group name to avoid conflicts, which is a valid suggestion. However, it also asks the author to verify potential issues with using github.ref, which violates the rule against asking the author to verify or double-check things. The first part of the comment is useful, but the second part should be removed.

Workflow ID: wflow_qLJD9vE13zSaDb2G

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[github-actions]

Included in release v0.3.9