fix dismiss all Dependabot review requests

[Pigbibi]

Policy

Automatically generated Pigbibi review requests are dismissed only when the request event itself was created by Dependabot. Requests made by maintainers are preserved. Major dependency updates remain open because the existing auto-merge workflow excludes semver-major updates.

What changed

• support dependabot[bot] and app/dependabot PR authors and event actors
• react directly to review_requested events
• serialize per-PR cleanup runs without cancelling the matching event
• verify the latest paginated timeline request still came from Dependabot immediately before deletion
• keep API failures visible while treating an already-removed request as success
• do not checkout or execute PR code

Validation

• 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 DELETE now runs based only on a single pre-delete timeline snapshot and no longer restores later human intent. If Pigbibi is manually re-requested after latest_request_actor is read but before this DELETE executes, the job will remove that fresh human review request as well, because GitHub stores only the current requested-reviewer state for that reviewer. This race is reachable on every review_requested run and causes a maintainer's manual request to be silently lost. (line 56)

Suggestion: Reintroduce a post-delete reconciliation step, or re-check the timeline/current requested reviewers immediately before and after DELETE so that a concurrent non-Dependabot review_requested event for Pigbibi is preserved or restored instead of being removed.

---

Review by Codex PR Review bot • PR

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c3df91cd7f

ℹ️ 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".