Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

A bot, but

> someone will enable the bot first and never get around to configuring it to, for example, not close an issue tagged as verified.

I don't understand this part. Aside from the fact that it's trivial to exclude certain tags (it's the same config file, and it's in the first example they give), doing this effectively makes your issue tracker useless as an issue tracker. Why not completely disable the issue tracker instead then?



Oh, I'm not saying it's great. What I'm saying is that the process often looks like this:

1. Release a project on GitHub

2. Get busy with other things / deluged in issues

3. “I don't have time for this. Let me install the auto-close bot!”

4. Issues get closed

5. [sometimes never] “I better configure the auto-close bot to only act on untriaged issues”




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: