question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Stale bot not closing issues

See original GitHub issue

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 Analytics

  • State:closed
  • Created 4 years ago
  • Comments:5

github_iconTop GitHub Comments

5reactions
issue-label-bot[bot]commented, Apr 23, 2019

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

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

1reaction
deepwellcommented, May 23, 2019

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

Read more comments on GitHub >

github_iconTop Results From Across the Web

Should I Stale or Should I Close? An Analysis of a Bot That ...
Our research investigates the adoption of the stale bot, which helps maintainers triaging abandoned issues and pull requests. We analyzed the bots' ...
Read more >
GitHub stale bot considered harmful : r/programming - Reddit
I think the problem is purely about issues, not merge requests. Closing merge request author doesn't want to fixup is way different than ......
Read more >
GitHub stale bot considered harmful - Drew DeVault's blog
The purpose of this bot is to automatically close GitHub issues after a period of inactivity, 60 days by default. You have probably...
Read more >
GitHub stale bot considered harmful - Hacker News
If I were to design this myself, I would argue that the correct way to treat an issue is not to have it...
Read more >
Should I Stale or Should I Close? An Analysis of a ... - Igor Wiese
investigates the adoption of the stale bot, which helps maintainers triaging abandoned issues and ... issues, one may close them when they are...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found