Fix stale bot cache issue by adding actions:write permission#3902
Fix stale bot cache issue by adding actions:write permission#3902tpantelis merged 2 commits intosubmariner-io:develfrom
Conversation
The stale workflow was experiencing a caching issue where issues were being perpetually skipped with the message "skipped due being processed during the previous run". This was caused by the workflow lacking the actions:write permission needed to delete/update the cache between runs. Without this permission, the stale action creates a cache of processed issues but cannot delete or update it in subsequent runs, resulting in a 403 error and issues getting stuck in a "perpetually processing" state. This fix adds the actions:write permission as recommended in: actions/stale#1131 Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
|
🤖 Created branch: z_pr3902/tpantelis/fix-stale-bot-cache-issue |
|
No actionable comments were generated in the recent review. 🎉 WalkthroughA GitHub Actions workflow permission was modified to grant write access to the actions permission in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
🤖 Closed branches: [z_pr3902/tpantelis/fix-stale-bot-cache-issue] |
Summary
This PR fixes a caching issue in the stale workflow where issues are being perpetually skipped with the message "skipped due being processed during the previous run".
Problem
The stale workflow was lacking the
actions:writepermission needed to delete/update the cache between runs. Without this permission:Solution
Add
actions:writeto the job permissions in.github/workflows/stale.yml.References
Summary by CodeRabbit