You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 20, 2023. It is now read-only.
In my understanding, wontfix has history and meaning and contextual baggage. In other contexts, it's used with intention after [thoughtful] consideration of a maintainer. I don't feel a bot should be tagging things wontfix, because it conveys more than the bot can know (or should know, unless we as maintainers of this bot are imposing an intended use).
I'm reading elsewhere that the desire is not to close issues, but to
mark issues as less relevant and
communicate that it needs attention to escape that mark
then can we default to something more neutral? I would suggest stale. Maintainers can filter on that (even if they're not using the "close" functionality, and get a sense of the "actual" valuable tickets are in their midst :)
The text was updated successfully, but these errors were encountered:
I don't know if we've reached consensus, but I'm going to close this issue since there are other issues and PRs on this topic(#67 & #76). Feel free to add any additional thoughts to those existing conversations.
In my understanding,
wontfix
has history and meaning and contextual baggage. In other contexts, it's used with intention after [thoughtful] consideration of a maintainer. I don't feel a bot should be tagging thingswontfix
, because it conveys more than the bot can know (or should know, unless we as maintainers of this bot are imposing an intended use).I'm reading elsewhere that the desire is not to close issues, but to
then can we default to something more neutral? I would suggest
stale
. Maintainers can filter on that (even if they're not using the "close" functionality, and get a sense of the "actual" valuable tickets are in their midst :)The text was updated successfully, but these errors were encountered: