Github messages for voidlinux
 help / color / mirror / Atom feed
From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] .github/workflows: Add a workflow for dealing with stale issues/prs
Date: Tue, 29 Mar 2022 03:52:55 +0200	[thread overview]
Message-ID: <20220329015255.U5zYFiE2yaCKSp7INPgm2FAIuV4WaQlSkjXjApdcV04@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: 703 bytes --]

There is an updated pull request by the-maldridge against master on the void-packages repository

https://github.com/the-maldridge/void-packages stale
https://github.com/void-linux/void-packages/pull/36399

.github/workflows: Add a workflow for dealing with stale issues/prs
This PR adds the [stale action](https://github.com/actions/stale) to try and keep an eye on things that are stale due to inactivity.  It will not act on any PR or issue that is assigned.  Right now it won't even make any changes, I just want it to run so we can evaluate what the rough impact would be of switching on a stale PR minder.

A patch file from https://github.com/void-linux/void-packages/pull/36399.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-stale-36399.patch --]
[-- Type: text/x-diff, Size: 1275 bytes --]

From bca0e727bc09cd6300188b4fbb0258e3aa564f57 Mon Sep 17 00:00:00 2001
From: Michael Aldridge <maldridge@voidlinux.org>
Date: Mon, 28 Mar 2022 20:48:50 -0500
Subject: [PATCH] .github/workflows: Add a workflow for dealing with stale
 issues/prs

---
 .github/workflows/stale.yml | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
 create mode 100644 .github/workflows/stale.yml

diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
new file mode 100644
index 000000000000..c759ef9459e0
--- /dev/null
+++ b/.github/workflows/stale.yml
@@ -0,0 +1,20 @@
+---
+name: Stale Cleanup
+
+on:
+  schedule:
+    - cron: '30 1 * * *'
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v4
+        with:
+          stale-issue-message: 'Issues become stale 90 days after last activity and are closed 7 days after that.  If this issue is still relevant bump it or assign it.'
+          stale-pr-message: 'Pull Requests become stale 90 days after last activity and are closed 7 days after that.  If this pull request is still relevant bump it or assign it.'
+          days-before-stale: 90
+          days-before-close: 7
+          debug-only: true
+          exempt-all-assignees: true
+          operations-per-run: 1000

  reply	other threads:[~2022-03-29  1:52 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 ` the-maldridge [this message]
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
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=20220329015255.U5zYFiE2yaCKSp7INPgm2FAIuV4WaQlSkjXjApdcV04@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).