dev: consider sonia-corporation/stale instead of actions/stale

[rootwork]

I recently switched from actions/stale to sonia-corporation/stale.

actions/stale appears to have no further active development, and sonia-corporation/stale has a nice feature: exempting from marking as stale all issues that are in a project (along with issues that are in milestones, or assigned to someone, both of which actions/stale already had). So if people are proposing features, simply accepting them by adding them to a project, like say a version release plan, will keep them from being marked stale without having to add extra labels.

sonia-corporation/stale also has a much more comprehensive documentation site: https://sonia-corporation.github.io/stale/

The Yaml keys in the workflow have different names but there's basically a 1:1 correspondence, so it was very fast to update my existing workflow to a new one.

Anyway just passing this along in case it's helpful!

[dec0dOS]

@rootwork, thanks a lot for sharing!
Seems to be that some commits has been done three days ago in the main branch. Is it really doesn't have any further development anymore?

[rootwork]

@dec0dOS You're right! Maybe it is in fact still in active development.

I appreciated the sonia version for its project option, but if that's not generally applicable then maybe actions/stale is still fine.

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍.
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!