From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, rebecca@bsdio.com
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Could we reconsider the GitHub stale PR bot please?
Date: Tue, 5 Nov 2024 14:08:27 +0100 [thread overview]
Message-ID: <bth7m745n7jbmaw2ybf6rgpk4fdtuadwkoxuwehke55gkp4egs@3c4golhrjx7p> (raw)
In-Reply-To: <471e9604-b611-4051-80b8-6ef7f244d2d7@bsdio.com>
On Mon, Oct 28, 2024 at 08:34:34PM -0600, Rebecca Cran wrote:
> See the attached screenshot or
> https://github.com/tianocore/edk2/pull/5907#issuecomment-2408745999 .
>
> The PR was marked stale by the bot and the PR author only responded two
> weeks later - which would have been one week too late.
>
> Fortunately I noticed and commented to keep it open, but I think we should
> reconsider the use of the stale bot.
Why is that a problem? I still get email notifications in case someone
adds a comment to a PR in closed (or merged) state, so updates do not go
unnoticed. Also it is always possible to re-open closed PRs.
take care,
Gerd
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120728): https://edk2.groups.io/g/devel/message/120728
Mute This Topic: https://groups.io/mt/109271104/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-11-05 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 2:34 [edk2-devel] Could we reconsider the GitHub stale PR bot please? Rebecca Cran
2024-10-29 5:43 ` Michael D Kinney
2024-10-29 6:04 ` Rebecca Cran
2024-10-29 17:42 ` Michael D Kinney
2024-11-05 13:08 ` Gerd Hoffmann [this message]
2024-11-05 13:52 ` Rebecca Cran
2024-11-05 15:36 ` Gerd Hoffmann
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-list 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=bth7m745n7jbmaw2ybf6rgpk4fdtuadwkoxuwehke55gkp4egs@3c4golhrjx7p \
--to=devel@edk2.groups.io \
/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