From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] Stale issues/pulls action
Date: Fri, 15 Apr 2022 08:50:24 +0200 [thread overview]
Message-ID: <20220415065024.EWqk85e3SsergTVtZiulyi9op5W_et-XFOf76a4wSV0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36657@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
New comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/issues/36657#issuecomment-1099896757
Comment:
> so it is not exactly a bug (as in code mistake/error), it just not a feature that the action offers
The documentation [states](https://github.com/actions/stale#remove-stale-when-updated):
> `remove-stale-when-updated`
Automatically remove the stale label when the issues or the pull requests are updated (based on [GitHub issue](https://docs.github.com/en/rest/reference/issues) field `updated_at`) or commented.
Default value: `true`
The action not acting like the documentation says it should is a bug
Edit: adding those relevant lines
```
[#34884] Pull request has been updated: true
[#34884] The option remove-stale-when-updated (https://github.com/actions/stale#remove-stale-when-updated) is: true
[#34884] The stale label should not be removed
```
(no message removed between them)
- It detects the PR has been updated: Correct
- It states it should remove stale when a pr is updated: Correct
- It decides that the label should not be removed: ???
next prev parent reply other threads:[~2022-04-15 6:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 13:30 [ISSUE] " dmarto
2022-04-14 23:44 ` classabbyamp
2022-04-15 0:13 ` dmarto
2022-04-15 0:19 ` dmarto
2022-04-15 0:20 ` dmarto
2022-04-15 0:21 ` dmarto
2022-04-15 0:23 ` dmarto
2022-04-15 6:43 ` 0x5c
2022-04-15 6:50 ` 0x5c [this message]
2022-04-15 8:05 ` 0x5c
2022-04-15 11:05 ` dmarto
2022-04-15 21:17 ` 0x5c
2022-06-20 23:22 ` dmarto
2022-06-20 23:45 ` 0x5c
2022-09-19 2:14 ` github-actions
2022-10-04 2:14 ` [ISSUE] [CLOSED] " github-actions
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=20220415065024.EWqk85e3SsergTVtZiulyi9op5W_et-XFOf76a4wSV0@z \
--to=0x5c@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).