Skip to content

Increasing the operations-per-run for stale issues GH action #3556

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 13, 2025

Conversation

petyaslavova
Copy link
Collaborator

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)

@petyaslavova petyaslavova added the maintenance Maintenance (CI, Releases, etc) label Mar 12, 2025
@petyaslavova petyaslavova merged commit daf6655 into master Mar 13, 2025
37 checks passed
@petyaslavova petyaslavova deleted the ps_update_stale_issue_action_config branch March 13, 2025 08:22
@petyaslavova petyaslavova added skip-changelog and removed maintenance Maintenance (CI, Releases, etc) labels Apr 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants