chore: dismiss Dependabot review requests

[Pigbibi]

What changed

• dismiss Pigbibi review requests automatically generated for Dependabot PRs
• recognize both dependabot[bot] and app/dependabot identities
• require the review-request event actor to be Dependabot
• re-check the latest Pigbibi review-request actor from the PR timeline immediately before deletion
• preserve later or concurrent review requests made by maintainers
• keep concurrent review-request runs instead of cancelling the matching cleanup
• use pull_request_target with metadata-only GitHub API access and no checkout

Why

These repositories already auto-merge eligible non-major Dependabot updates after CI, but CODEOWNERS creates redundant review notifications. Event-actor and timeline checks let the workflow remove only bot-generated requests without touching human review requests, including race conditions while a run is queued.

Validation

• verified automatic CODEOWNERS timeline actor on a historical Dependabot PR
• verified both supported Dependabot identities
• verified requested reviewer, event actor, and latest timeline actor conditions
• verified API errors fail instead of being treated as no match
• verified no checkout or execution of PR code
• bash syntax check
• git diff --check

[github-actions]

🤖 Codex PR Review

✅ Merge allowed: 1 finding(s) reported but none are blocking

ℹ️ Other Findings

1. 🟡 [MEDIUM] Logic in .github/workflows/dependabot_review_request_cleanup.yml

The helper only looks at review_requested timeline entries for Pigbibi and ignores later review_request_removed events. If a maintainer requests Pigbibi and then removes that request while this queued run is still executing, the post-delete recheck will still see the maintainer as the latest requester and will re-add Pigbibi, resurrecting a review request that a human explicitly dismissed. (line 28)

Suggestion: When deciding whether to preserve or restore the reviewer, inspect both review_requested and review_request_removed events and act only if the latest relevant timeline event is still a human review_requested. Before restoring, also re-read the current reviewRequests set to confirm the reviewer is actually supposed to be present.

---

Review by Codex PR Review bot • PR

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c11fdcfe71

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f205758efd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e990f38d1b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".