breaking-change-cross-version-status.yaml

name: "Breaking Change(Cross-Version) - Set Status"

on:
  # Must run on pull_request_target instead of pull_request, since the latter cannot trigger on
  # labels from bot accounts in fork PRs. pull_request_target is also more similar to the other
  # trigger "workflow_run" -- they are both privileged and run in the target branch and repo --
  # which simplifies implementation.
  pull_request_target:
    types:
      # Run workflow on default types, to update status as quickly as possible.
      - opened
      - synchronize
      - reopened
      # Depends on labels, so must re-evaluate whenever a relevant label is manually added or removed.
      - labeled
      - unlabeled
  workflow_run:
    # Trigger on both old and new names, to handle the rename more gracefully
    workflows:
      [
        "Breaking Change(Cross-Version) - Analyze Code",
        "\\[TEST-IGNORE\\] Breaking Change(Cross-Version) - Analyze Code",
      ]
    types: [completed]

permissions:
  actions: read
  contents: read
  issues: read
  pull-requests: read
  statuses: write

jobs:
  breaking-change-cross-version-status:
    name: Set Breaking Change(Cross-Version) Status
    uses: ./.github/workflows/_reusable-set-check-status.yaml
    with:
      monitored_workflow_name: "Breaking Change(Cross-Version) - Analyze Code"
      required_check_name: "Breaking Change(Cross-Version)"
      overriding_label: "BreakingChange-Approved-Benign,BreakingChange-Approved-BugFix,BreakingChange-Approved-UserImpact,BreakingChange-Approved-BranchPolicyException,BreakingChange-Approved-Previously,BreakingChange-Approved-Security,BreakingChange-Approved-Retired,Versioning-Approved-Benign,Versioning-Approved-BugFix,Versioning-Approved-PrivatePreview,Versioning-Approved-BranchPolicyException,Versioning-Approved-Previously,Versioning-Approved-Retired,Versioning-Approved-NotReleased"