Github messages for voidlinux
 help / color / mirror / Atom feed
* [PR PATCH] .github/workflows: Add a workflow for dealing with stale issues/prs
@ 2022-03-29  1:52 the-maldridge
  2022-03-29  1:52 ` [PR PATCH] [Updated] " the-maldridge
                   ` (10 more replies)
  0 siblings, 11 replies; 12+ messages in thread
From: the-maldridge @ 2022-03-29  1:52 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

There is a new 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: 1199 bytes --]

From cd46c6438bbfd21fc5dbe21930abc3b5ccde4b8e 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 | 18 ++++++++++++++++++
 1 file changed, 18 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..2c79d3a89b58
--- /dev/null
+++ b/.github/workflows/stale.yml
@@ -0,0 +1,18 @@
+---
+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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [PR PATCH] [Updated] .github/workflows: Add a workflow for dealing with stale issues/prs
  2022-03-29  1:52 [PR PATCH] .github/workflows: Add a workflow for dealing with stale issues/prs the-maldridge
@ 2022-03-29  1:52 ` the-maldridge
  2022-03-29  2:08 ` 0x5c
                   ` (9 subsequent siblings)
  10 siblings, 0 replies; 12+ messages in thread
From: the-maldridge @ 2022-03-29  1:52 UTC (permalink / raw)
  To: ml

[-- 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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: .github/workflows: Add a workflow for dealing with stale issues/prs
  2022-03-29  1:52 [PR PATCH] .github/workflows: Add a workflow for dealing with stale issues/prs the-maldridge
  2022-03-29  1:52 ` [PR PATCH] [Updated] " the-maldridge
@ 2022-03-29  2:08 ` 0x5c
  2022-03-29 13:10 ` subnut
                   ` (8 subsequent siblings)
  10 siblings, 0 replies; 12+ messages in thread
From: 0x5c @ 2022-03-29  2:08 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 237 bytes --]

New comment by 0x5c on void-packages repository

https://github.com/void-linux/void-packages/pull/36399#issuecomment-1081325066

Comment:
This would essentially take care of https://github.com/void-linux/void-packages/issues/36253 fully

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: .github/workflows: Add a workflow for dealing with stale issues/prs
  2022-03-29  1:52 [PR PATCH] .github/workflows: Add a workflow for dealing with stale issues/prs the-maldridge
  2022-03-29  1:52 ` [PR PATCH] [Updated] " the-maldridge
  2022-03-29  2:08 ` 0x5c
@ 2022-03-29 13:10 ` subnut
  2022-03-29 13:10 ` subnut
                   ` (7 subsequent siblings)
  10 siblings, 0 replies; 12+ messages in thread
From: subnut @ 2022-03-29 13:10 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 647 bytes --]

New comment by subnut on void-packages repository

https://github.com/void-linux/void-packages/pull/36399#issuecomment-1081851695

Comment:
I guess we could tag the stale PRs with the _"stale-pending_reply"_ tag, and ping the author requesting him to reply if they are still interested. Then wait for a specified time period (3 weeks?)
 - If they reply, remove the  _stale-pending_reply_ tag
 - If they do not reply, remove the _stale-pending_reply_, add the _stale_ tag
   - Wait again for some time period
   - If author replies within said time period, remove _stale_ tag
   - If time period ends without author replying, **close the PR**

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: .github/workflows: Add a workflow for dealing with stale issues/prs
  2022-03-29  1:52 [PR PATCH] .github/workflows: Add a workflow for dealing with stale issues/prs the-maldridge
                   ` (2 preceding siblings ...)
  2022-03-29 13:10 ` subnut
@ 2022-03-29 13:10 ` subnut
  2022-03-29 13:10 ` subnut
                   ` (6 subsequent siblings)
  10 siblings, 0 replies; 12+ messages in thread
From: subnut @ 2022-03-29 13:10 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 723 bytes --]

New comment by subnut on void-packages repository

https://github.com/void-linux/void-packages/pull/36399#issuecomment-1081851695

Comment:
I guess we could tag the stale PRs with the _"stale-pending_reply"_ tag, and ping the author requesting him to reply if they are still interested. Then wait for a specified time period (3 weeks?)
 - If they reply, remove the  _stale-pending_reply_ tag
 - If they do not reply, remove the _stale-pending_reply_, add the _stale_ tag
   - Wait again for some time period
   - If author replies within said time period, remove _stale_ tag
   - If time period ends without author replying, **close the PR**

EDIT: It's all speculation. I don't even know if GitHub APIs allow this.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: .github/workflows: Add a workflow for dealing with stale issues/prs
  2022-03-29  1:52 [PR PATCH] .github/workflows: Add a workflow for dealing with stale issues/prs the-maldridge
                   ` (3 preceding siblings ...)
  2022-03-29 13:10 ` subnut
@ 2022-03-29 13:10 ` subnut
  2022-03-29 13:37 ` classabbyamp
                   ` (5 subsequent siblings)
  10 siblings, 0 replies; 12+ messages in thread
From: subnut @ 2022-03-29 13:10 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 738 bytes --]

New comment by subnut on void-packages repository

https://github.com/void-linux/void-packages/pull/36399#issuecomment-1081851695

Comment:
I guess we could tag the stale PRs with the _"stale-pending_reply"_ tag, and ping the author requesting him to reply if they are still interested. Then wait for a specified time period (3 weeks?)
 - If they reply, remove the  _stale-pending_reply_ tag
 - If they do not reply, remove the _stale-pending_reply_, add the _stale_ tag
   - Wait again for some time period
   - If author replies within said time period, remove _stale_ tag
   - If time period ends without author replying, **close the PR**

EDIT: It's all speculation for the future. I don't even know if GitHub API allows this.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: .github/workflows: Add a workflow for dealing with stale issues/prs
  2022-03-29  1:52 [PR PATCH] .github/workflows: Add a workflow for dealing with stale issues/prs the-maldridge
                   ` (4 preceding siblings ...)
  2022-03-29 13:10 ` subnut
@ 2022-03-29 13:37 ` classabbyamp
  2022-03-29 13:51 ` subnut
                   ` (4 subsequent siblings)
  10 siblings, 0 replies; 12+ messages in thread
From: classabbyamp @ 2022-03-29 13:37 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 256 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36399#issuecomment-1081883663

Comment:
i believe that's what the stale action in this automates. maybe not the exact method but the overall concept 

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: .github/workflows: Add a workflow for dealing with stale issues/prs
  2022-03-29  1:52 [PR PATCH] .github/workflows: Add a workflow for dealing with stale issues/prs the-maldridge
                   ` (5 preceding siblings ...)
  2022-03-29 13:37 ` classabbyamp
@ 2022-03-29 13:51 ` subnut
  2022-03-29 18:00 ` Chocimier
                   ` (3 subsequent siblings)
  10 siblings, 0 replies; 12+ messages in thread
From: subnut @ 2022-03-29 13:51 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 833 bytes --]

New comment by subnut on void-packages repository

https://github.com/void-linux/void-packages/pull/36399#issuecomment-1081851695

Comment:
I guess we could tag the stale PRs with the _"stale-pending_reply"_ tag, and ping the author requesting him to reply if they are still interested. Then wait for a specified time period (3 weeks?)
 - If they reply, remove the  _stale-pending_reply_ tag
 - If they do not reply, remove the _stale-pending_reply_, add the _stale_ tag
   - Wait again for some time period
   - If author replies within said time period, remove _stale_ tag
   - If time period ends without author replying, **close the PR**

~EDIT: It's all speculation for the future. I don't even know if GitHub API allows this.~
EDITv2: :facepalm: I hadn't even seen the files added by this PR before making this comment

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: .github/workflows: Add a workflow for dealing with stale issues/prs
  2022-03-29  1:52 [PR PATCH] .github/workflows: Add a workflow for dealing with stale issues/prs the-maldridge
                   ` (6 preceding siblings ...)
  2022-03-29 13:51 ` subnut
@ 2022-03-29 18:00 ` Chocimier
  2022-03-29 18:16 ` 0x5c
                   ` (2 subsequent siblings)
  10 siblings, 0 replies; 12+ messages in thread
From: Chocimier @ 2022-03-29 18:00 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 297 bytes --]

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/pull/36399#issuecomment-1082206002

Comment:
Closing PRs is fine, but reported bugs don't go away just because they are old. Issues should be rather marked as stale and left open.

Ok for dry run.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: .github/workflows: Add a workflow for dealing with stale issues/prs
  2022-03-29  1:52 [PR PATCH] .github/workflows: Add a workflow for dealing with stale issues/prs the-maldridge
                   ` (7 preceding siblings ...)
  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
  10 siblings, 0 replies; 12+ messages in thread
From: 0x5c @ 2022-03-29 18:16 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 402 bytes --]

New comment by 0x5c on void-packages repository

https://github.com/void-linux/void-packages/pull/36399#issuecomment-1082221400

Comment:
> Closing PRs is fine, but reported bugs don't go away just because they are old. Issues should be rather marked as stale and left open.
> 
> Ok for dry run.

Oh yeah issues should probably not be auto-closed
A review of the issue backlog seems to be in order tho

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [PR PATCH] [Updated] .github/workflows: Add a workflow for dealing with stale issues/prs
  2022-03-29  1:52 [PR PATCH] .github/workflows: Add a workflow for dealing with stale issues/prs the-maldridge
                   ` (8 preceding siblings ...)
  2022-03-29 18:16 ` 0x5c
@ 2022-03-30  2:05 ` the-maldridge
  2022-03-30  2:06 ` [PR PATCH] [Merged]: " the-maldridge
  10 siblings, 0 replies; 12+ messages in thread
From: the-maldridge @ 2022-03-30  2:05 UTC (permalink / raw)
  To: ml

[-- 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 f841eea1cfc53d84dd21ca08daa056a7b2f6dcc7 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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [PR PATCH] [Merged]: .github/workflows: Add a workflow for dealing with stale issues/prs
  2022-03-29  1:52 [PR PATCH] .github/workflows: Add a workflow for dealing with stale issues/prs the-maldridge
                   ` (9 preceding siblings ...)
  2022-03-30  2:05 ` [PR PATCH] [Updated] " the-maldridge
@ 2022-03-30  2:06 ` the-maldridge
  10 siblings, 0 replies; 12+ messages in thread
From: the-maldridge @ 2022-03-30  2:06 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 537 bytes --]

There's a merged pull request on the void-packages repository

.github/workflows: Add a workflow for dealing with stale issues/prs
https://github.com/void-linux/void-packages/pull/36399

Description:
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.

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2022-03-30  2:06 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-29  1:52 [PR PATCH] .github/workflows: Add a workflow for dealing with stale issues/prs the-maldridge
2022-03-29  1:52 ` [PR PATCH] [Updated] " the-maldridge
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

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).