You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue here seems to be that your workflow file is defining closed days as "in addition to" stale days. The bot used to interpret closed days independently of stale days, so 7 would mean "close issues after 7 days if they are marked stale".
I recently changed the behavior because it's confusing. The bot will now only close issues after 97 days (as you intended) but you installed it before that update.
I also added more logging by default in case unexpected behavior happens in the future, so you will be able to point to the logs and see why the bot did what it did.
Apologies for the confusing behavior here. Please let me know if you have any further issues in the new runs.
Thanks for the info. Do I need to do something in order to get the latest version?
Also, just to make sure, If I add a stale tag manually, will this bot close the issue after 7 days and not just after 97? Also removing the stale label is defined as "touching" the issue so that it won't close?
Thanks again!
I have yesterday added this action to my project.
The flow ran tonight and closed half of my issues.
They were stale, but instead of only marking as stale and wait a week it closed it immediately.
This seems like a critical bug to me.
See here:
https://github.com/IsraelHikingMap/Site/blob/master/.github/workflows/stale.yml
https://github.com/IsraelHikingMap/Site/issues?q=is%3Aissue+is%3Aclosed+sort%3Aupdated-desc
The text was updated successfully, but these errors were encountered: