Increasing the operations-per-run for stale issues GH action by petyaslavova · Pull Request #3556 · redis/redis-py (original) (raw)

Pull Request check-list

Please make sure to review and check all of these items:

• Do tests and lints pass with this change?
• Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
• Is the new or changed code fully tested?
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
• Is there an example added to the examples folder (if applicable)?
• Was the change added to CHANGES file?

NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.

Description of change

Current configuration is able to cover the following issues and PRs:
Processed items: 132
├── Processed issues: 95
└── Processed PRs : 37

As a result lots of issues marked as stale are not closed by the automated actions.
We can still increase a lot more, but as a start, I prefer to double the ops per run and check if it will be enough (Github API rate used: 10
Github API rate remaining: 14989)