Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/ci-failure-analyst.yml
Original file line number Diff line number Diff line change
Expand Up @@ -18,21 +18,21 @@
# Docs: https://github.com/petry-projects/.github-private/blob/main/docs/aw/ci-failure-analyst.md
# ─────────────────────────────────────────────────────────────────────────────

name: "CI Failure Analyst"
name: 'CI Failure Analyst'

on:
check_run:
types: [completed]

permissions:
pull-requests: write
issues: write # post/read PR comments via the Issues comments API
issues: write # post/read PR comments via the Issues comments API
actions: read
contents: read
checks: read

concurrency:
group: "ci-failure-analyst-${{ github.event.check_run.head_sha }}"
group: 'ci-failure-analyst-${{ github.event.check_run.head_sha }}'
cancel-in-progress: false

jobs:
Expand Down
10 changes: 10 additions & 0 deletions .github/workflows/dev-lead.yml
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,16 @@ on:

permissions: {}

concurrency:
# One active run per repo; ci-relay (check_run) keeps an ephemeral per-SHA slot
# so it can fire immediately without blocking or being blocked by the dispatch queue.
group: >-
${{
github.event_name == 'check_run' && format('dev-lead-ci-relay-{0}', github.event.check_run.head_sha) ||
'dev-lead'
}}
cancel-in-progress: false
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Preserve queued dev-lead runs in concurrency group

With cancel-in-progress: false and no queue setting, GitHub Actions keeps only one pending run per concurrency group by default and cancels older pending runs when new events arrive. Because this workflow is triggered by high-frequency events (issue_comment, review comments, PR sync, etc.), overlapping activity while one run is in progress will silently drop intermediate dev-lead invocations, so some user/CI signals may never be processed. Add queue: max (or split groups) if you need all queued events to run.

Useful? React with 👍 / 👎.


jobs:
dev-lead:
uses: petry-projects/.github-private/.github/workflows/dev-lead-reusable.yml@main
Comment on lines +48 to 52
Expand Down
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -10,3 +10,4 @@ playwright-report/
# compliance-ci-trigger
# ci-trigger-298
.dev-lead/
.dev-lead/
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

The entry .dev-lead/ is already present in this file on line 12 (and lines 8-9). This duplicate entry is redundant and can be removed.

Loading