Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update stale bot config #6858

Closed
wants to merge 1 commit into from
Closed

update stale bot config #6858

wants to merge 1 commit into from

Conversation

arvidn
Copy link
Owner

@arvidn arvidn commented May 11, 2022

No description provided.

@arvidn arvidn mentioned this pull request May 11, 2022
@AllSeeingEyeTolledEweSew
Copy link
Contributor

This doesn't address my largest complaint about stalebot, which is that it has apparent bugs, and will close an issue despite activity. See #5154 and #6198

# Issues with these labels will never be considered stale
exemptLabels:
- pinned
- security
- todo
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the effect of this is that I'll just prompt you to add todo to any issue I open

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's not an obvious problem to me.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it seems backwards that high quality reports should carry the burden of requesting the "good issue" label, arguing why they deserve it, knowing to do so in the first place, re-requesting it if you forget to apply the label when responding to the ticket, and dealing with the additional noise.

I make high quality reports and I want all the burden to be on low-quality reporters :)

@arvidn
Copy link
Owner Author

arvidn commented May 11, 2022

I should research whether there are some configuration options of stale bot to improve or fix this. Perhaps it just has the wrong default.

@ghost
Copy link

ghost commented May 12, 2022

428 issues closed by stale bot 😮

@userdocs
Copy link

userdocs commented May 13, 2022

Most of my issues closed by stale bot have been generic build stuff I forgot to close or was never resolved but became obsolete from using newer versions and stuff so I can't say it caused me any drama but I think it should work like this:

Stale bot should message the issue and ask the op if they want to keep it open and if not can they please tag it can close it manually.

So basically interact with the OP act in response to that outcome.

Maybe after x amount of non responses default to a behaviour.

I think using it to encourage the OP manage the issue is the best first step. At least that way they wont just get their issue closed?

Maybe stale bot forces someone to tag the issue with a easily filterable tag before closing so relevant issues can be filtered when searching? Good for python binding specific issues for example.

Dead stuff with no response will get closed for lack of reply.

@stale
Copy link

stale bot commented Aug 12, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Aug 12, 2022
@stale stale bot closed this Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants