Skip to content

chore: trigger security review on label add - #6754

Merged
DmytroZaichenkoDev merged 1 commit into
development-1.0from
chore/security-review-labeled-trigger
May 18, 2026
Merged

DmytroZaichenkoDev merged 1 commit into
development-1.0from
chore/security-review-labeled-trigger

Conversation

@DmytroZaichenkoDev

Copy link
Copy Markdown
Contributor

Summary

  • Adds `labeled` to the security-review workflow's `pull_request` activity types.
  • Closes the UX gap where applying the `security-review` label after PR creation (including via `gh pr create --label`, which applies labels in a separate API call) did not fire the workflow.
  • Job-level `if: contains(... 'security-review')` continues to gate execution, so other label changes start the workflow but the job skips immediately.

Context

Observed on test PR #6753: the initial `opened` event fired with an empty labels array (label was applied a moment later), so the job was skipped. A subsequent push made it run because `synchronize` saw the label present.

🤖 Generated with Claude Code

Adds 'labeled' to the security-review workflow's pull_request activity
types so applying the 'security-review' label after the PR is opened
fires the workflow. Previously the workflow only ran on opened or
synchronize, so labels applied post-creation (e.g. via gh pr create
--label, which applies the label as a separate API call) didn't trigger
a run. The existing label-presence check in the job's if condition
continues to gate execution.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@DmytroZaichenkoDev
DmytroZaichenkoDev merged commit b6345ab into development-1.0 May 18, 2026
3 checks passed
@DmytroZaichenkoDev
DmytroZaichenkoDev deleted the chore/security-review-labeled-trigger branch May 18, 2026 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant