Github messages for voidlinux
 help / color / mirror / Atom feed
* [PR PATCH] .github/workflows/stale.yml: ignore tracking issues
@ 2022-08-23  9:22 classabbyamp
  2022-11-05  2:19 ` abenson
  2022-11-05  4:37 ` [PR PATCH] [Merged]: " classabbyamp
  0 siblings, 2 replies; 3+ messages in thread
From: classabbyamp @ 2022-08-23  9:22 UTC (permalink / raw)
  To: ml

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

There is a new pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages tracking-stale-ignore
https://github.com/void-linux/void-packages/pull/38853

.github/workflows/stale.yml: ignore tracking issues
I created a new label for tracking issues. it's logical that they should be excluded from stalebot.

If a tracking label isn't wanted, it can be removed.

Related: should the existing [`inactive`](https://github.com/void-linux/void-packages/labels/inactive) label be merged with the `stale` label? there's only one open issue with it

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

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

From 9a1ad14eda3044a721ebc357e318fe180a822c83 Mon Sep 17 00:00:00 2001
From: classabbyamp <5366828+classabbyamp@users.noreply.github.com>
Date: Sat, 20 Aug 2022 18:03:52 -0400
Subject: [PATCH] .github/workflows/stale.yml: ignore tracking issues

---
 .github/workflows/stale.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
index d0fb383e4424..5be1f599dcec 100644
--- a/.github/workflows/stale.yml
+++ b/.github/workflows/stale.yml
@@ -22,4 +22,4 @@ jobs:
           exempt-all-assignees: true
           ascending: true
           operations-per-run: 250
-          exempt-issue-labels: 'request,bug'
+          exempt-issue-labels: 'request,bug,tracking'

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

* Re: .github/workflows/stale.yml: ignore tracking issues
  2022-08-23  9:22 [PR PATCH] .github/workflows/stale.yml: ignore tracking issues classabbyamp
@ 2022-11-05  2:19 ` abenson
  2022-11-05  4:37 ` [PR PATCH] [Merged]: " classabbyamp
  1 sibling, 0 replies; 3+ messages in thread
From: abenson @ 2022-11-05  2:19 UTC (permalink / raw)
  To: ml

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

New comment by abenson on void-packages repository

https://github.com/void-linux/void-packages/pull/38853#issuecomment-1304379169

Comment:
I agree with both proposals.

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

* Re: [PR PATCH] [Merged]: .github/workflows/stale.yml: ignore tracking issues
  2022-08-23  9:22 [PR PATCH] .github/workflows/stale.yml: ignore tracking issues classabbyamp
  2022-11-05  2:19 ` abenson
@ 2022-11-05  4:37 ` classabbyamp
  1 sibling, 0 replies; 3+ messages in thread
From: classabbyamp @ 2022-11-05  4:37 UTC (permalink / raw)
  To: ml

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

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

.github/workflows/stale.yml: ignore tracking issues
https://github.com/void-linux/void-packages/pull/38853

Description:
I created a new label for tracking issues. it's logical that they should be excluded from stalebot.

If a tracking label isn't wanted, it can be removed.

Related: should the existing [`inactive`](https://github.com/void-linux/void-packages/labels/inactive) label be merged with the `stale` label? there's only one open issue with it

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

end of thread, other threads:[~2022-11-05  4:37 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-08-23  9:22 [PR PATCH] .github/workflows/stale.yml: ignore tracking issues classabbyamp
2022-11-05  2:19 ` abenson
2022-11-05  4:37 ` [PR PATCH] [Merged]: " classabbyamp

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