Is your feature request related to a problem? Please describe.
It has been observed that pull requests are waiting for reviews for more than weeks and remain open for long time. This will delay feedback from the PR requester (contributor) and may cause merge conflicts. This also might add complexity to monitor the backlog and review for maintainers.
Describe the solution you'd like
Add a scheduled GitHub Actions workflow that runs on a weekly cadence and identifies PRs that have been open or waiting for review for more than 7 days.
The workflow summary can be as given below :
- PR title
- PR number
- PR author
- PR URL
- Date opened
- Days waiting
- Current reviewers, if any
- Labels, if useful
Automate to generate a weekly email to configured maintainers/owners/contributors.
Describe alternatives you've considered
Instead of relying on emails, the workflow could:
- Create a weekly “PRs awaiting review” issue and update as part of weekly checks
- Post a comment on stale PRs referencing maintainers.
- Send notifications to Slack, Teams, or another project channel.
A GitHub issue/comment-based approach may be easier to maintain because it does not require SMTP credentials or recipient email management.
Additional context
None to report
Is your feature request related to a problem? Please describe.
It has been observed that pull requests are waiting for reviews for more than weeks and remain open for long time. This will delay feedback from the PR requester (contributor) and may cause merge conflicts. This also might add complexity to monitor the backlog and review for maintainers.
Describe the solution you'd like
Add a scheduled GitHub Actions workflow that runs on a weekly cadence and identifies PRs that have been open or waiting for review for more than 7 days.
The workflow summary can be as given below :
Automate to generate a weekly email to configured maintainers/owners/contributors.
Describe alternatives you've considered
Instead of relying on emails, the workflow could:
A GitHub issue/comment-based approach may be easier to maintain because it does not require SMTP credentials or recipient email management.
Additional context
None to report