# Summary
This PR updates the triage bots schedule and raises the
operations-per-run limit.
# Details
Previous actions have been implemented using a defensive approach to
test the bots runtime and rate limits.
At the moment the single run at 6 in the morning utilized `0,0066`% of
our hourly GitHub API rate limit.
With those settings we will be done with the currently open 800 issues
in ~1/3 year.
This PR updates the schedule to hourly and raises the API limit to 100
(3x of the default, out of 4500 API calls per hour, based of the stale
action execution log).
- Hourly will make the bot much more responsive (after the 800 issues
have been ~~purged~~ processed).
- A higher rate will allow the current state to be processed faster and
will provide better response to higher workloads in the future.
- The cache continues to handle any workload above 100
operations-per-run.
# Summary
This PR adds the missing actions write permission to the triage bot.
# Details
The actions write permission is required to access the actions cache
that is needed for operations-per-run continuity. This one was simply
missing.
# Summary
This PR fixes the to-be exempt labels on issues and PRs that the stale
action should ignore when trying to mark them as stale.
# Details
The label exempt regex syntax isn't supported [anymore?], this resulted
in the setting being ignored.
This PR also contains light cleaning, removal of defaults, update of
cron to daily to utilize the rate limit per run without getting rate
limited.
# On merge
Please trigger the action manually on merge so the output is immediately
available to verify the fix.
The documentation provides no info on the formatting of the labels
within their comma brackets, it might be possible they have another
format in code (e.g. `"Bot Ignore"` -> `"bot-ignore"`?).
Not a real breaking behavior if wrong but possibly annoying and open to
fix afterwards.
# Summary
This PR adds a GitHub action workflow to automatically triage issues and
pull requests regarding their activity.
## Intent
The repository features a lot of really old and no longer relevant
issues. Those issues are commonly not maintained by their authors and
processing them manually is not feasible.
By adding this workflow we got a very transparent and user friendly way
to keep the issues clear and meaningful: Issues that will be opened get
more attention and don't drown in the sea of stale issue. Issues marked
as replicable are easier to spot for anyone (developers *and* any other
contributor), making them easier to get picked.
Similar for PRs: I have seen multiple manual clean ups of dead pull
requests. This can be automated as well. For the start, I have opted out
of auto closing PRs, but this can be easily added afterwards if it gains
interest.
Generally, this keeps the repository cleaner, making it easier to
interact with issues posted. This helps anyone looking for an issue to
fix, which is, by my own experience, an easy for new contributors to
start.
## Settings
### Issues
Issues will be marked as stale after 60 days of no activity. If the
issue has been labeled replicable, it won't get marked as stale. Any
activity will remove the stale label again.
After additional 30 days the issue will be closed if its still marked as
stale.
### Pull requests
Pull requests will be marked as stale after 60 days of no activity. If
the pull requests has been labeled by any discussion label, it won't get
marked as stale. Any activity will remove the stale label again.
Pull request will never be auto-closed, unlike issues.
