probot / stale

A GitHub App built with Probot that closes abandoned Issues and Pull Requests after a period of inactivity.
https://probot.github.io/apps/stale/
ISC License
1.25k stars 212 forks source link

Stale bot not closing issues #199

Closed deepwell closed 5 years ago

deepwell commented 5 years ago

On April 10th, 2019 I setup stale bot to mark issues as stale, and then auto close them. It's been almost 2 weeks and there has been no change on the tickets (some which are 2 years old that I expected to be marked as stale). Can you take a look and let me know if something is not configured correctly? Thanks.

Issues: https://github.com/deepwell/issues-v2/issues

.github/stale.yml looks like this:

# Number of days of inactivity before an issue becomes stale
daysUntilStale: 365
# Number of days of inactivity before a stale issue is closed
daysUntilClose: 14
# Issues with these labels will never be considered stale
exemptLabels:
  - security
  - type: data integrity
# Limit to only issues or pulls
only: issues
# Label to use when marking an issue as stale
staleLabel: wontfix
# Comment to post when marking an issue as stale. Set to `false` to disable
markComment: >
  This issue has been automatically marked as stale because it has not had
  activity in the last year. It will be closed if no further activity occurs. Thank you
  for your contributions.
# Comment to post when closing a stale issue. Set to `false` to disable
closeComment: true
issue-label-bot[bot] commented 5 years ago

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.88. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

mbanon commented 5 years ago

I am having the same issue...

AdmiringWorm commented 5 years ago

@deepwell I think your problem here is due to an invalid yaml file (I had the same problem).

Change the exempt label type: data integrity to be in quotes, then I believe it should work for you. (ie - "type: data integrity")

EDIT: Could also be a problem with the last line closeComment: true, from my understanding, this is meant to be either a message that will be commented on the issue when it gets closed, or false. So it may be that true isn't a valid value in this case.

deepwell commented 5 years ago

Thanks @AdmiringWorm, it was both adding the quotes to the exemptLabels, and removing the closeComment: true portion that fixed it for me.

Gustry commented 5 years ago

So you need to close your issue if it's fixed.