merge-pull-requests

You can automatically triage and merge open GitHub pull requests by running a workflow that discovers PRs from Dependabot, Codex, Jules, and manual contributions, then classifies them based on staleness before executing safe merge actions.

Staleness detection for pending pull requests works by analyzing PR metadata to classify them as fresh, stale, or obsolete, which helps suggest appropriate actions like safe merging or batch closing obsolete PRs with explanatory comments.

Yes, you can automatically merge pull requests while respecting CI checks, approvals, and branch policies by using an automated merge workflow that validates CI status, handles drafts and forks, and applies the correct merge strategy.

The best way to handle bulk closing of obsolete pull requests on GitHub is to use an automated batch closing process that identifies stale PRs and closes them in bulk while leaving explanatory comments for contributors.

Automated PR merging does work with vendor review integration by optionally running multi-vendor reviews specifically for large or unreviewed pull requests before proceeding with the safe merge actions.

Limitations of automating pull request triage include needing to properly handle draft PRs and forks, as the automated workflow must validate approvals and CI status before it can safely merge these specific contribution types.