From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] .github/workflows/stale.yml: increase operations limit
Date: Fri, 15 Apr 2022 01:45:50 +0200 [thread overview]
Message-ID: <20220414234550.6a7uoctda9SQrkE2VYdZPqDQzjdwJvQCbccRfvqsIm0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36699@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
There is an updated pull request by classabbyamp against master on the void-packages repository
https://github.com/classabbyamp/void-packages increase-stale-limit
https://github.com/void-linux/void-packages/pull/36699
.github/workflows/stale.yml: increase operations limit
By setting [`ascending`](https://github.com/actions/stale#ascending) to `true`, the most stale issues and PRs will be caught first. By increasing the operations limit from the default (30) to 100, more stale issues/PRs will be caught each run, increasing the speed of the burndown.
This implements some of the suggestions from #36657
A patch file from https://github.com/void-linux/void-packages/pull/36699.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-increase-stale-limit-36699.patch --]
[-- Type: text/x-diff, Size: 904 bytes --]
From bb026942c2b84fdc7c9819e16de9d726da4ed330 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Thu, 14 Apr 2022 19:30:06 -0400
Subject: [PATCH] .github/workflows/stale.yml: increase operations limit
By setting `ascending` to `true`, the most stale issues and PRs will be
caught first. By increasing the operations limit from the default (30)
to 250, more stale issues/PRs will be caught each run, increasing the
speed of the burndown.
---
.github/workflows/stale.yml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
index 91ac19e4f638..9dbb76cd2a3d 100644
--- a/.github/workflows/stale.yml
+++ b/.github/workflows/stale.yml
@@ -17,3 +17,5 @@ jobs:
days-before-stale: 90
days-before-close: 14
exempt-all-assignees: true
+ ascending: true
+ operations-per-run: 250
next prev parent reply other threads:[~2022-04-14 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 23:32 [PR PATCH] ./github/workflows/stale.yml: " classabbyamp
2022-04-14 23:36 ` [PR PATCH] [Updated] .github/workflows/stale.yml: " classabbyamp
2022-04-14 23:36 ` classabbyamp
2022-04-14 23:45 ` classabbyamp [this message]
2022-04-15 0:15 ` dmarto
2022-04-15 0:49 ` [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=20220414234550.6a7uoctda9SQrkE2VYdZPqDQzjdwJvQCbccRfvqsIm0@z \
--to=classabbyamp@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).