Ban github actions that automatically close "stale" issues

[barneysspeedshop]

Why are you starting this discussion?

Product Feedback

What GitHub Actions topic or product is this about?

Workflow Configuration

Discussion Details

It should be against the TOS to create github actions that automatically mark issues as stale and close them. It's completely dismissive, hurts the community, and prevents developers from wanting to engage.

If you haven't checked to confirm that the issue is fixed, issues should not be closed.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Vivek-k001]

They’re saying GitHub Actions that automatically close “stale” issues are harmful because they shut down conversations too quickly without confirming if the problem is really fixed, which can discourage community involvement. They think this practice should be against GitHub’s rules.

[barneysspeedshop]

This is an accurate summary of the request

[hariiee1277-dotcom]

Delete or rename .github/workflows/stale.yml to stop the stale bot.

[barneysspeedshop]

That's fine if you run the repo, but I don't consider that a solution. It shouldn't be used. You document the bug, properly submit a github issue with steps to reproduce it, and there's no problem with your but report issue, but the maintainers just don't get around to fixing it. Now you have to bump the issue forever just because you reported it?

[dserodio]

The maintainers of an Open Source project don't owe you anything. If you don't like how a given project is managed, you're free to fork it and run your fork as you please.

[robertlerry14-hash]

In .github/stale.yml, add exempt_issues: ['*'] to prevent auto-closing.

[barneysspeedshop]

That's fine if you run the repo, but I don't consider that a solution. It shouldn't be used. You document the bug, properly submit a github issue with steps to reproduce it, and there's no problem with your but report issue, but the maintainers just don't get around to fixing it. Now you have to bump the issue forever just because you reported it?