meta(gha): Deploy action stale.yml

[chadwhitacre]

I are a bot, here to deploy stale.yml. 🤖

[AbhiPrasad]

🚀

[github-actions]

size-limit report

Path	Size
@sentry/browser - CDN Bundle (gzipped)	22.33 KB (-0.01% 🔽)
@sentry/browser - Webpack	23.31 KB (0%)
@sentry/react - Webpack	23.34 KB (0%)
@sentry/browser + @sentry/tracing - CDN Bundle (gzipped)	29.79 KB (0%)

[vladanpaunovic]

LGTM.
Thanks @chadwhitacre! 🚀

[chadwhitacre]

@AbhiPrasad @vladanpaunovic When we merge this it will cause a flood of old issues to be marked stale. Are you ready for that? If you want, you can review old issues and apply Status: Backlog to any that you know you want to keep. Otherwise, expect 200+ bot comments and notifications from GitHub! 😅

Let me know ...

[lobsterkatie]

To Chad's point, I think we need to do at least a surface once-over before we pull the trigger on this. FWIW I would set a longer threshold on the staleness, also, but regardless, a chance for us to mark things "backlog" before we do this would be good.

I'd also vote for an additional, non-status no-stale tag or something, because there are sometimes issues we want to keep open where the actual status (blocked, waiting for information, etc) is useful to know, and having to lose that information to keep the issue from closing feels like a step back from the better tagging we've been doing.