From: subnut <subnut@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: .github/workflows: Add a workflow for dealing with stale issues/prs
Date: Tue, 29 Mar 2022 15:51:37 +0200 [thread overview]
Message-ID: <20220329135137.UpmsdLjnXjvl4h8EirbfmkqoW_gTGq2uA39wmMjwN80@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36399@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
New comment by subnut on void-packages repository
https://github.com/void-linux/void-packages/pull/36399#issuecomment-1081851695
Comment:
I guess we could tag the stale PRs with the _"stale-pending_reply"_ tag, and ping the author requesting him to reply if they are still interested. Then wait for a specified time period (3 weeks?)
- If they reply, remove the _stale-pending_reply_ tag
- If they do not reply, remove the _stale-pending_reply_, add the _stale_ tag
- Wait again for some time period
- If author replies within said time period, remove _stale_ tag
- If time period ends without author replying, **close the PR**
~EDIT: It's all speculation for the future. I don't even know if GitHub API allows this.~
EDITv2: :facepalm: I hadn't even seen the files added by this PR before making this comment
next prev parent reply other threads:[~2022-03-29 13:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 1:52 [PR PATCH] " the-maldridge
2022-03-29 1:52 ` [PR PATCH] [Updated] " the-maldridge
2022-03-29 2:08 ` 0x5c
2022-03-29 13:10 ` subnut
2022-03-29 13:10 ` subnut
2022-03-29 13:10 ` subnut
2022-03-29 13:37 ` classabbyamp
2022-03-29 13:51 ` subnut [this message]
2022-03-29 18:00 ` Chocimier
2022-03-29 18:16 ` 0x5c
2022-03-30 2:05 ` [PR PATCH] [Updated] " the-maldridge
2022-03-30 2:06 ` [PR PATCH] [Merged]: " the-maldridge
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=20220329135137.UpmsdLjnXjvl4h8EirbfmkqoW_gTGq2uA39wmMjwN80@z \
--to=subnut@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).