Github messages for voidlinux
 help / color / mirror / Atom feed
From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [RFC] Give stale PRs 2 weeks to show signs of life
Date: Mon, 11 Apr 2022 03:39:23 +0200	[thread overview]
Message-ID: <20220411013923.WjPWTKM1ghZ2jSte-43py0e5QFxIbujvRiuls6JbflM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36253@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]

Closed issue by 0x5c on void-packages repository

https://github.com/void-linux/void-packages/issues/36253

Description:
### ... then nuke the ones that didn't.

## Rationale
The backlog is enormous, scary, and full of PRs that don't meet quality requirements, are waiting (for months) for requested changes, and/or have generally been abandoned. There's even PRs that no longer have an author (#29665, #30909). 
This idea was mentioned multiple times in the IRC channel by multiple people, with a positive response.

## How
1. Set a cutoff amount of inactivity, ie: 6 months
2. Get the list of PRs matching that inactivity to a file, ie: `gh pr list -L 2000 -S 'updated:<=2021-09-20' > file.tsv`
    The issue number is the first column
4. Using a script and the GH API, do for each PR in the list:
    1. Apply the already-existing `inactive` tag
    2. Send a message explaining that the PR will be closed in two weeks if it doesn't get any activity.
5. Wait two weeks
6. Close marked PRs that didn't get any updates.
    This part could be done automatically if searching for `label:inactive updated:<=[date of script run]T[time of script run]`, although it will miss PRs where the activity was just "I don't use void anymore". I suspect this will not be a big problem considering how dead the backlog is.

      parent reply	other threads:[~2022-04-11  1:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21  3:17 [ISSUE] " 0x5c
2022-03-21  3:25 ` subnut
2022-03-21  3:31 ` 0x5c
2022-03-22 17:58 ` classabbyamp
2022-03-22 18:04 ` tibequadorian
2022-03-22 19:59 ` 0x5c
2022-03-22 19:59 ` 0x5c
2022-03-22 20:14 ` tibequadorian
2022-03-22 21:38 ` 0x5c
2022-03-22 23:51 ` 0x5c
2022-04-11  1:39 ` 0x5c
2022-04-11  1:39 ` 0x5c [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220411013923.WjPWTKM1ghZ2jSte-43py0e5QFxIbujvRiuls6JbflM@z \
    --to=0x5c@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).