Comments (3)
That would really complicate the logic, and I think kind of defeats the purpose. The point of the auto-closer is to close issues that have shown no activity. If you prompt activity by warning people, the metric gets cloudy and you don't know if any activity occurring is organic or just a "bump" to make sure it doesn't get closed.
On the technical side, it complicates the logic dramatically, because the bot comment counts as activity, so we'd need to loop through comments to check and see if any are from the bot to really figure out if there's any activity.
So I'm ๐ for both reasons.
from eslint-github-bot.
To give some more context around what prompted this idea: Iโve been noticing a non-trivial number of bug reports that get auto-closed without any response from the team. Since they might be valid bug reports that still need to be evaluated, those issues then get reopened with an apology, which can make the process feel hostile to the issue author.
I think we might also be able to solve this at a process level by ensuring we actively triage issues and respond to any issues we remove the triage label from.
I think your points are fair and this might not be a targeted enough approach to solve this. Iโm going to close this and continue thinking about it.
from eslint-github-bot.
For reference, a popular GitHub App "stale" bot warns inactive issues before closing.
from eslint-github-bot.
Related Issues (20)
- Feature: Support canary releases HOT 3
- Update release-monitor to use 4-week release cadence HOT 2
- Commit message check failing HOT 1
- Update: Helpful error messages for commit message format check HOT 13
- New label: fill issue template HOT 5
- Switch from master to main for primary branch HOT 1
- Updates for the new triage process
- shorten the text in the comment, to make less annoying HOT 6
- Test of the new bot HOT 1
- Auto-deploy failed HOT 1
- commit message checks missing HOT 3
- TSC Meeting issues not automatically created HOT 1
- Donโt add TSC meeting/release issues to triage board HOT 4
- Deploy doesn't work HOT 3
- Respecting the optional scope in Conventional Commits HOT 3
- Deploy failing HOT 1
- Bot still adds Triage labels to PRs HOT 3
- Bot needs updating to be deployed HOT 1
- npm ERR! cb.apply is not a function HOT 1
- another deploying error HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from eslint-github-bot.