From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] .github/workflows/stale.yml: don't tag issues with request label as s…
Date: Fri, 15 Apr 2022 03:50:37 +0200 [thread overview]
Message-ID: <20220415015037.e0qwlh_6odu84exsp4xi1hxP4eb28h8emaOARrHykSM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36609@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
There is an updated pull request by Duncaen against master on the void-packages repository
https://github.com/Duncaen/void-packages stale-request-label
https://github.com/void-linux/void-packages/pull/36609
.github/workflows/stale.yml: don't tag issues with request label as s…
None
A patch file from https://github.com/void-linux/void-packages/pull/36609.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-stale-request-label-36609.patch --]
[-- Type: text/x-diff, Size: 655 bytes --]
From d2a08f6f76a1c9fe66701c9b9b3c072a4872b676 Mon Sep 17 00:00:00 2001
From: Duncaen <duncaen@voidlinux.org>
Date: Sun, 10 Apr 2022 04:47:01 +0200
Subject: [PATCH] .github/workflows/stale.yml: don't tag issues with request
label as stale
---
.github/workflows/stale.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
index 9dbb76cd2a3d..160897fedef1 100644
--- a/.github/workflows/stale.yml
+++ b/.github/workflows/stale.yml
@@ -19,3 +19,4 @@ jobs:
exempt-all-assignees: true
ascending: true
operations-per-run: 250
+ exempt-issue-labels: request
next prev parent reply other threads:[~2022-04-15 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 2:49 [PR PATCH] " Duncaen
2022-04-15 1:50 ` Duncaen [this message]
2022-04-15 1:51 ` [PR PATCH] [Closed]: " 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=20220415015037.e0qwlh_6odu84exsp4xi1hxP4eb28h8emaOARrHykSM@z \
--to=duncaen@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).