X Tutup
Skip to content

Delete stale.yml#1543

Merged
StephanTLavavej merged 1 commit intomicrosoft:masterfrom
StephanTLavavej:stale-potato-chip
Mar 1, 2026
Merged

Delete stale.yml#1543
StephanTLavavej merged 1 commit intomicrosoft:masterfrom
StephanTLavavej:stale-potato-chip

Conversation

@StephanTLavavej
Copy link
Member

Automatically closing stale issues and PRs is an abomination. It is incredibly infuriating and dismissive, and makes me not want to interact with a project ever again, and I imagine most contributors feel the same way. If I take the time to report an issue, or prepare a PR, and the maintainers are busy through absolutely no fault of my own, and they just throw my issue or PR in the trash because it's been on their desk for a while, that's just stomping over my hard work that I tried to contribute out of the goodness of my heart.

We should get rid of this thing. In the STL, I have long fought (for nearly 20 years!) against automatically closing issues as "stale" or "wontfix" purely based on time. If a bug is a bug, then it remains a bug, even if the maintainers are too busy at the moment.

Now, sometimes an issue or PR does need to get closed because it isn't actionable, or too much divergence has accumulated between it and the current state of main, or it's addressing some deprecated area that will be outright removed in the future, etc. Manually closing issues and PRs when this happens, with an explanation of why it's necessary, is fine. I am purely objecting to the unthinking time-based auto-stale machinery.

Copy link
Collaborator

@kennykerr kennykerr left a comment

Choose a reason for hiding this comment

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

This doesn’t really address the underlying issue, which is that the project does not have active maintainers. At least with the stale workflow, interested developers get a reminder that the issue exists and at least some effort should be taken to acknowledge the lack of progress. That seems preferable to me, but if everyone prefer issues to remain open but forgotten that’s fine too. Either way it’s not ideal. 🥺

@StephanTLavavej
Copy link
Member Author

Thanks Kenny. Yes, the underlying problem is unaffected, but leaving issues/PRs open is a better way to acknowledge the state of reality. Issue reporters / PR contributors usually post comments when they want to know what's happening with an issue/PR. Leaving issues open also makes it easier to see if someone's encountering a problem that others have had before.

@StephanTLavavej StephanTLavavej merged commit dcbdcc8 into microsoft:master Mar 1, 2026
75 checks passed
@StephanTLavavej StephanTLavavej deleted the stale-potato-chip branch March 1, 2026 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

X Tutup