[wp-trac] [WordPress Trac] #61887: Add automation to close stale pull requests

WordPress Trac noreply at wordpress.org
Fri Aug 16 12:11:44 UTC 2024


#61887: Add automation to close stale pull requests
------------------------------+------------------------------
 Reporter:  swissspidy        |       Owner:  (none)
     Type:  task (blessed)    |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------

Comment (by dmsnell):

 > Update the PR from the base branch if it's super out of date

 Of note, Github already maintains an updated merge of each PR into its
 target branch up to the point of merge conflicts. This is what shows on a
 PR's diff view. That is, there's no need to update from the base branch
 unless a conflict prevents Github from updating the `/merge` branch for
 the PR, and if there's a conflict, this can't be done automatically.

 https://fluffyandflakey.blog/2022/12/21/what-is-a-github-pull-request-
 merge-branch/

 > an automated GitHub Action that goes through old PRs and closes them

 Might toss out the idea of leaving a comment and asking the PR author to
 confirm if it's still necessary, or ask to add a label to keep it open.
 Can be quite frustrating to have long-running work frequently closed
 without asking. I know most PRs can be relatively short lived, but as you
 know, sometimes work takes years to get done and requires a cascade of
 changes to the system before they can be finally reviewed and merged.

 Alternatively, instead of closed, could they be switched to draft status?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/61887#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list