3.0.1 version removed the stale label on some issues

[actions]

3.0.1 version removed the stale label on some issues

[hross]

yes this is related. adding a comment will reset the stale counter, so in this case you have 365 more days until the issue gets marked stale. incidentally your close days is not additive to stale (I wonder if it should be) so the issue will get closed immediately after it gets marked stale with the configuration you currently have set up.

[hross]

you can turn the behavior off with the remove-stale-when-updated flag

[Gustry]

Thanks, I noticed the weird behaviour this morning : 3liz/lizmap-web-client#392
The bot is confused :)

Well, I wanted to the behaviour remove-stale-when-updated so when a user comments, it resets the counter. But this should have an exception for the current token used for the bot.

[hross]

Sorry about the bug here. I fixed this behavior here: #73

If you use the v3 label in the action you should pick it up automatically next time.

[hross]

New release is here and at the v3 tag: https://github.com/actions/stale/releases/tag/v3.0.3

[DanTup]

incidentally your close days is not additive to stale

Can you clarify what this means? It sounds like the close time wouldn't wouldn't be added on to the stale time, though I expected that it would - and the examples have lower close values than stale:

        days-before-stale: 30
        days-before-close: 5

I'm unsure how I've configured mine now (it's as the sample above) :-)

[Gustry]

The workflow ran this morning using version 3.0.4:
https://github.com/3liz/lizmap-web-client/blob/master/.github/workflows/stale_issue.yml

But I can still notice this issue on this ticket:
3liz/lizmap-web-client#1254
The bot added the label but removed it too at the same time.

But not this one:
3liz/lizmap-web-client#1247

I can't reopen my own issue.

[Gustry]

I have updated to the latest version 3.0.6, still the same issue:
Example 3liz/lizmap-web-client#1601