ci: remove redundant concurrency block from issue-labeler

[dhc-tech]

Remove redundant concurrency block from issue-labeler to permanently eliminate workflow file validation errors on GitHub Actions.

Summary by Sourcery

Improve issue and pull request labeling workflows by making concurrency reliable, using current issue state, and removing automatic AI review triggers.

Bug Fixes:

• Use live issue data when calculating labels to prevent stale labels during rapid consecutive edits.

Enhancements:

• Move issue-labeler concurrency control to the workflow level and remove its job-level condition.
• Remove automatic AI review comments from pull request labeling.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The issue-labeler workflow is simplified by removing the redundant job-level condition and concurrency block, leaving the triage job to proceed with its existing steps while eliminating the configuration that caused GitHub Actions validation errors.

File-Level Changes

Change	Details	Files
Remove the issue-labeler job's conditional guard and concurrency configuration to avoid GitHub Actions workflow validation errors.	Delete the issue-event null check from the triage job. Delete the issue-number-based concurrency group and cancel-in-progress setting.	.github/workflows/issue-labeler.yml

---

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.

[github-actions]

@sourcery-ai review
@coderabbitai review

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 14c7c84f-d2eb-40ab-aae5-02cb14999a4b

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/clean-issue-labeler-workflow

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[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=".github/workflows/issue-labeler.yml" line_range="24-26" />
<code_context>
     name: triage
     runs-on: ubuntu-latest
-    if: github.event.issue != null
-    concurrency:
-      group: issue-metadata-${{ github.event.issue.number }}
-      cancel-in-progress: true
     steps:
       - name: Checkout repository
</code_context>
<issue_to_address>
**issue (bug_risk):** Removing the per-issue concurrency group allows multiple `edited` runs for the same issue to execute concurrently. Each run computes `finalLabels` from its event's potentially stale `issue.labels` snapshot and then calls `setLabels`, so an older run can finish last and overwrite labels calculated from a newer edit.

**Triggers:** When an issue is edited again before the previous labeling run completes.

**Suggested fix:** Retain a valid per-issue concurrency group, or otherwise serialize label updates for the same issue.
</issue_to_address>

Sourcery assessment

Needs a human reviewer. 1 finding to address first, and removing concurrency can allow overlapping runs to race while updating issue labels, and removing the event guard can run the job for events without an issue. Reverting restores the previous behavior, but any incorrect labels or metadata written before the revert would need to be repaired or the job rerun.

Blocking findings: .github/workflows/issue-labeler.yml:26

---

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

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}