close-labeler workflow uses break instead of continue, dropping the QA label on multi-issue PRs

[kobihikri]

Summary

.github/workflows/close-labeler.yml uses break where it needs continue, so a PR that closes more than one issue can silently miss getting the QA label.

The loop over the PR's closing issues is:

for (const node of result.repository.pullRequest.closingIssuesReferences.nodes) {
  const shouldQA = node.labels.edges.find(edge => edge.node.name === "Enhancement" || edge.node.name === "Bug") != null
  if (!shouldQA) {
    break        // <-- aborts the whole loop on the first non-Bug/Enhancement issue
  }
  // ... add "QA" label
}

Because it breaks (rather than continues) on the first issue that isn't a Bug/Enhancement, any Bug/Enhancement issues that come after it in the list are never reached, so the QA label isn't added.

Steps to reproduce

A PR whose Closes #… references resolve, in order, to [Documentation, Bug, Enhancement]:

• current (break): QA label added to none
• expected (continue): QA label added to the Bug and the Enhancement

I ran the exact loop body in Node to confirm the order-dependent difference.

Expected behavior

Skip the non-qualifying issue and keep checking the rest.

Fix

Change the one word break → continue. Happy to open the PR if useful.

_{AI-assisted; I verified the workflow logic myself.}

[moosairfaan]

I'd like to take this on — opening a PR shortly.

[kobihikri]

Thanks @moosairfaan — please go ahead, it's all yours. Happy to review or help if useful.