From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: .github/workflows/stale.yml: update to v6
Date: Fri, 30 Sep 2022 09:09:53 +0200 [thread overview]
Message-ID: <20220930070953.dndeK08rbadPpxD05_-yzTyO5MlvKCg5eK9VmdoNkCM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39537@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
There's a merged pull request on the void-packages repository
.github/workflows/stale.yml: update to v6
https://github.com/void-linux/void-packages/pull/39537
Description:
This fixes a bug where a stale issue/PR that gets updated without a comment remains stale indefinitely and never gets closed (actions/stale#715).
The only "breaking" change in that update is that the default close reason has changed to "not planned". That seems like a more desirable default anyways.
A current example of the bug can be found in #37283.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **NO**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2022-09-30 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 6:55 [PR PATCH] " 0x5c
2022-09-30 7:09 ` the-maldridge [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=20220930070953.dndeK08rbadPpxD05_-yzTyO5MlvKCg5eK9VmdoNkCM@z \
--to=the-maldridge@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).