Problem

Currently, multiple events (e.g., issue opened + issue edited) can trigger the triage workflow simultaneously, leading to race conditions or duplicate bot comments.

Proposed Solution

Add concurrency control to the GitHub Actions workflow to ensure only one triage process runs per issue/PR at a time.

Implementation:

Add a concurrency group to the workflow files:

concurrency:
  group: simili-${{ github.event.issue.number || github.event.pull_request.number }}
  cancel-in-progress: false

Benefits:

• Prevents redundant bot comments.
• Avoids race conditions during label application.
• Saves GitHub Actions minutes by not running overlapping triages.