Github messages for voidlinux
 help / color / mirror / Atom feed
From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: .github/workflows/stale.yml: do not close issues labelled as bug
Date: Tue, 02 Aug 2022 19:44:51 +0200	[thread overview]
Message-ID: <20220802174451.jwhNxj2Cskk01TX-wIhIgNXdeu0OkqRpZ80j08K09FU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38272@inbox.vuxu.org>

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

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

.github/workflows/stale.yml: do not close issues labelled as bug
https://github.com/void-linux/void-packages/pull/38272

Description:
We need a way to exclude issues form autoclosing. Or stop autoclosing any issues.

PR #36411 was built with excluding [`label:bug -label:needs-testing`](https://github.com/void-linux/void-packages/issues?q=is%3Aopen+is%3Aissue+label%3Abug+-label%3Aneeds-testing+) in mind, but this is not expressible with workflow. Let `bug` label make issues not stale.

      reply	other threads:[~2022-08-02 17:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 16:45 [PR PATCH] " Chocimier
2022-08-02 17:44 ` Chocimier [this message]

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=20220802174451.jwhNxj2Cskk01TX-wIhIgNXdeu0OkqRpZ80j08K09FU@z \
    --to=chocimier@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).