use latest commit of stalebot action, tweak configuration accordingly

[rrennick]

Changes proposed in this Pull Request:

This PR updates stalebot to use the latest commit to main of the stalebot action. # 1033 adding caching to the stalebot action which allows it to continue processing from the previous run. Once it has processed all PRs/issue it resets and starts the scan from the first issue/PR.

Accordingly, this PR includes the following configuration changes:

• replaces the 4 schedules with an hourly schedule
• Reduces the number of items scanned to 100 per run

This should complete a scan of all open items within 24 hours. After the block merge the scan is likely to take closer to 28 hours which would be 6 complete scans every 7 days. This schedule should work fine for both scenarios.

A secondary benefit to this configuration change is it should allow adding a scan schedule for PRs once we have discussed a good time frame for this.

How to test the changes in this Pull Request:

Using the WooCommerce Testing Instructions Guide, include your detailed testing instructions:

1. YML review

Changelog entry

• Automatically create a changelog entry from the details below.

Significance

• Patch
• Minor
• Major

Type

• Fix - Fixes an existing bug
• Add - Adds functionality
• Update - Update existing functionality
• Dev - Development related task
• Tweak - A minor adjustment to the codebase
• Performance - Address performance issues
• Enhancement - Improvement to existing functionality

Message

Comment

[github-actions]

Hi @ObliviousHarmony,

Apart from reviewing the code changes, please make sure to review the testing instructions as well.

You can follow this guide to find out what good testing instructions should look like:
https://github.com/woocommerce/woocommerce/wiki/Writing-high-quality-testing-instructions

[github-actions]

Test Results Summary

Commit SHA: d516d3b

Test 🧪	Passed ✅	Failed 🚨	Broken 🚧	Skipped ⏭️	Unknown ❔	Total 📊	Duration ⏱️
API Tests	259	0	0	2	0	261	0m 37s
E2E Tests	243	0	0	4	0	247	13m 25s

---

To view the full API test report, click here.
To view the full E2E test report, click here.
To view all test reports, visit the WooCommerce Test Reports Dashboard.

[ObliviousHarmony]

It's worth noting that as per the documentation, operations-per-run is counting API calls rather than issues. Since processing an issue may require multiple API calls, it's possible for 100 operations to be more like 30 issues. An operations-per-run limit of 300 probably gets us closer to 100 issues per hour.

[ObliviousHarmony]

Thanks for tolerating me @rrennick!