Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Processing less than 24 issues per day
See original GitHub issueThe limitPerRun configuration option, which limits the number of actions per hour, has a minimum of 1. This means that when enabling stale bot on a repo with lots of old issues, the minimum is getting pings on 24 issues per day.
Does anyone here have ideas how to reduce that?
I’m interested to know if it’s possible to get somewhere between 1-5 issues a day, so that they can be reviewed appropriately.
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Automation service limits | Automation for Jira Data Center ...
If a query returns more issues than this limit, the UI shows a warning and only allow schedules of, at most, 4 times...
Read more >Data limits for Universal Analytics properties - Google Support
Processing latency is 24-48 hours. Standard accounts that send more than 200,000 sessions per day to Analytics will result in the reports being...
Read more >Evaluation and management FAQs - Novitas Solutions
Is the documentation of history and examination required when scoring office/outpatient services under the revised 2021 guidelines?
Read more >What is payroll processing? - ADP
Processing payroll means compensating employees for their work. ... nonexempt workers to a minimum wage of not less than $7.25 per hour (effective...
Read more >ENTRY SUMMARY ACCEPTANCE AND REJECTION POLICY
1.5 Rejected entry summaries must be returned to CSP in valid status with payment within 2 working days from day of rejection or...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is blocked pending an upstream fix of https://github.com/probot/scheduler/issues/32.
You could fork stale and edit it’s use of scheduler to utilize these options.
Or you could build this into core stale and open a PR and as long as the default is still an hour, that should be fine.