Skip to content

GH-34389: [Dev] Verify issue assignment before reporting success - #53870

Open
limadog9 wants to merge 1 commit into
apache:mainfrom
limadog9:fix-pr-bot-assignment-34389
Open

limadog9 wants to merge 1 commit into
apache:mainfrom
limadog9:fix-pr-bot-assignment-34389

Conversation

@limadog9

@limadog9 limadog9 commented Oct 15, 2026 •

Copy link
Copy Markdown

Rationale for this change

Closes #34389.

GitHub can silently ignore an issue assignment when the contributor is not yet eligible to be assigned. The PR bot currently announces success even when the returned issue has no assignees.

What changes are included in this PR?

Send the assignees as an array and verify that the assignment response includes the PR creator before posting the success message. If assignment was ignored, link the issue and ask the contributor to leave a comment requesting assignment by a committer or collaborator, following the contributor documentation.

Add dependency-free Node regression tests and run them in a read-only Dev workflow job.

Are these changes tested?

  • node --test .github/workflows/dev_pr/*.test.js — 6 passed. Three cases fail with the original implementation.
  • Coverage includes successful assignment, silently ignored assignment, a different returned assignee, an already assigned issue, and unrelated PR titles.
  • JavaScript syntax checks, workflow YAML parsing, and git diff --check pass.

Are there any user-facing changes?

The bot reports assignment success only when GitHub confirms it. Contributors whose automatic assignment is rejected receive a link and instructions to request assignment instead of an incorrect success message.

### Rationale for this change

Closes apache#34389.

GitHub can silently ignore an issue assignment when the contributor is not yet eligible to be assigned. The PR bot currently announces success even when the returned issue has no assignees.

### What changes are included in this PR?

Send the assignees as an array and verify that the assignment response includes the PR creator before posting the success message. If assignment was ignored, link the issue and ask the contributor to leave a comment requesting assignment by a committer or collaborator, following the contributor documentation.

Add dependency-free Node regression tests and run them in a read-only Dev workflow job.

### Are these changes tested?

- `node --test .github/workflows/dev_pr/*.test.js` — 6 passed. Three cases fail with the original implementation.
- Coverage includes successful assignment, silently ignored assignment, a different returned assignee, an already assigned issue, and unrelated PR titles.
- JavaScript syntax checks, workflow YAML parsing, and `git diff --check` pass.

### Are there any user-facing changes?

The bot reports assignment success only when GitHub confirms it. Contributors whose automatic assignment is rejected receive a link and instructions to request assignment instead of an incorrect success message.
@github-actions

Copy link
Copy Markdown

⚠️ GitHub issue #34389 has been automatically assigned in GitHub to PR creator.

@github-actions github-actions Bot added the awaiting review Awaiting review label Oct 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting review Awaiting review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Dev] Some assignments from the PR bot fail due to anti-spam protection

1 participant