From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: Rebecca Cran <rebecca@bsdio.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Could we reconsider the GitHub stale PR bot please?
Date: Tue, 29 Oct 2024 17:42:13 +0000 [thread overview]
Message-ID: <CO1PR11MB492901E95AE9E70457FB12ADD24B2@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <e80199f2-7a1a-4923-910b-091929019688@app.fastmail.com>
Hi Rebecca,
Here is the link to the full description of the action and all of its settings
https://github.com/actions/stale
Here is the link to the edk2 repo GitHub Action workflow that uses this action
https://github.com/tianocore/edk2/blob/master/.github/workflows/stale.yml
Current settings ate 60 days to slate and 7 days to close.
I think you are suggesting changing those to 180 days and 90 days.
Do you want to create a PR with those changes?
Mike
> -----Original Message-----
> From: Rebecca Cran <rebecca@bsdio.com>
> Sent: Monday, October 28, 2024 11:04 PM
> To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>
> Subject: Re: [edk2-devel] Could we reconsider the GitHub stale PR bot
> please?
>
> How about 6 months? And closing it if there’s been no follow-up to the
> bot’s comment after 3 months?
>
> Rebecca
>
> On Mon, Oct 28, 2024, at 11:43 PM, Michael D Kinney wrote:
> > I believe the timeframe to mark one stale is configurable.
> >
> > Is there a proposal for a different wait time?
> >
> > Mike
> >
> >> -----Original Message-----
> >> From: Rebecca Cran <rebecca@bsdio.com>
> >> Sent: Monday, October 28, 2024 7:35 PM
> >> To: devel@edk2.groups.io
> >> Cc: Kinney, Michael D <michael.d.kinney@intel.com>
> >> Subject: Could we reconsider the GitHub stale PR bot please?
> >>
> >> 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.
> >>
> >>
> >> --
> >> Rebecca
> >
> >
> >
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120693): https://edk2.groups.io/g/devel/message/120693
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]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2024-10-29 17:42 UTC|newest]
Thread overview: 4+ 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 [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-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=CO1PR11MB492901E95AE9E70457FB12ADD24B2@CO1PR11MB4929.namprd11.prod.outlook.com \
--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