Skip to content

chore: increase operation per run in stale workflow - #2564

Merged
MatteoGabriele merged 2 commits into
npmx-dev:mainfrom
MatteoGabriele:chore/stale-workflow-increase-operation-per-run
Apr 18, 2026
Merged

chore: increase operation per run in stale workflow#2564
MatteoGabriele merged 2 commits into
npmx-dev:mainfrom
MatteoGabriele:chore/stale-workflow-increase-operation-per-run

Conversation

@MatteoGabriele

@MatteoGabrieleMatteoGabriele commented Apr 18, 2026

Copy link
Copy Markdown
Member

🧭 Context

Running 100 operations per run was likely too conservative considering the size of npmx, and we weren't able to process all the items we had.
Currently, we have 210 issues, 97 PRs, and comments to review, so we need to expand our quota.

📚 Description

Increase the operation-per-run to 500 and see if this is enough. We have 5000 API requests per hour, and this workflow runs once at 2 am, so it's still really safe.

@vercel

vercelBot commented Apr 18, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
npmx.devReadyReadyPreview, CommentApr 18, 2026 1:34pm
2 Skipped Deployments
ProjectDeploymentActionsUpdated (UTC)
docs.npmx.devIgnoredIgnoredPreviewApr 18, 2026 1:34pm
npmx-lunariaIgnoredIgnoredApr 18, 2026 1:34pm

Request Review

@coderabbitai

coderabbitaiBot commented Apr 18, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

Updated the GitHub Actions stale workflow to increase the operations-per-run input for actions/stale from 100 to 500, enabling the workflow to handle more stale issue/PR operations per execution.

Changes

Cohort / File(s)Summary
GitHub Actions Configuration
.github/workflows/close-stale.yml
Changed actions/stale input operations-per-run from 100 to 500.

Possibly related PRs

  • feat: add stale workflow #2555: Modifies the same .github/workflows/close-stale.yml workflow and adjusts actions/stale configuration related to operations-per-run.
🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check nameStatusExplanation
Title check✅ PassedThe title accurately reflects the main change: increasing operations per run in the stale workflow configuration.
Description check✅ PassedThe pull request description clearly relates to the changeset, providing context about why the operations-per-run limit needed to be increased and explaining the rationale based on the repository's issue and PR volume.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov

codecovBot commented Apr 18, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

@graphierosgraphieros left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The syntax looks ok to me !

@MatteoGabriele
MatteoGabriele added this pull request to the merge queueApr 18, 2026
Merged via the queue into npmx-dev:main with commit e365dd4Apr 18, 2026
24 checks passed
@MatteoGabriele
MatteoGabriele deleted the chore/stale-workflow-increase-operation-per-run branch April 18, 2026 14:01
@github-actionsgithub-actionsBot mentioned this pull request Apr 18, 2026
ayo-run pushed a commit to ayo-run/npmx.dev that referenced this pull request Aug 5, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@MatteoGabriele@graphieros