Stale does not close issues

Hi all,
love GitHub and Actions even more.

I have setup an action to close my issues after 30 days of inactivity.

name: "Close stale issues"
on:
  schedule:
    - cron: "0 0 * * *"

jobs:
  stale:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/stale@v3
        with:
          repo-token: ${{ secrets.GITHUB_TOKEN }}
          stale-issue-message: 'This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days'
          days-before-stale: 30
          days-before-close: 5

stale label is correctly added after 30 days but the issue is not closed after 35 days.
why?

thanks

Hi @sblantipodi,

I copied your code and it works fine on my side, issue is closed.
My workflow: https://github.com/weide-zhou/ticket25/runs/741321456?check_suite_focus=true
My issue: https://github.com/weide-zhou/ticket25/issues/1


What’s your action log?
Is it possible that the issue doesn’t reach the timeline 35 days?

Thanks.

thanks for the answer @weide-zhou, I appreciate it.

this is the issue:

this the workflow:

and this the log:

Could you try setting debug-only:true as an argument to the Action to see if any further logs are outputted?

@github-support
thanks for the answer

this is the output with the debug only true option. it doesn’t help a lot I think.

here the complete log

Hi @sblantipodi,

According to your action log, the issue is updated which cause it’s not old enough to close.

2020-06-07T15:23:28.6311513Z Issue #1 has been updated: true
2020-06-07T15:23:28.6312068Z Stale issue is not old enough to close yet (hasComments? false, hasUpdate? true

However looks the last update is at 2020-05-29T00:13:35Z which should meets the timeline 5 days.
I notice there’s already a same issue on tracking: https://github.com/actions/stale/issues/91
You can comment on it and check if there’s any fix by github developing team.

Thanks.

ok thanks, I will follow that issue.

Hi @sblantipodi,

There is a fix on the issue now, could you please have a double check?


Thanks.

it seems that it works now