8000 chore: increase stale operations per run by Hebilicious · Pull Request #22501 · nuxt/nuxt · GitHub
[go: up one dir, main page]
Skip to content

chore: increase stale operations per run #22501

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Aug 5, 2023
Merged

chore: increase stale operations per run #22501

merged 1 commit into from
Aug 5, 2023

Conversation

Hebilicious
Copy link
Member
@Hebilicious Hebilicious commented Aug 5, 2023 •
edited
Loading

🔗 Linked issue

❓ Type of change

  • 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • 👌 Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Looking at the first workflow run , it looks like the bot successfully closed 3 issues .
There's room to increase the amount of operations per run as there is a lot of issues to go through.

Statistics:
Processed items: 74
├── Processed issues: 55
└── Processed PRs   : 19
Closed issues: 3
Added issues labels: 3
Added issues comments: 3
Fetched items: 100
Fetched items events: 10
Fetched items comments: 10
Operations performed: 30

We could also try to run the bot more frequently.

I'm wary of being rate limited for all the other worfklows if we increase this number too much though...

Does nuxt has a github entreprise account ? Otherwise it looks like we are rate limited to 1000 request/hour; therefore increasing to 100 should be safe (assuming 1 operation = 1request)

📝 Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@danielroe danielroe merged commit 8eefc06 into nuxt:main Aug 5, 2023
@github-actions github-actions bot mentioned this pull request Aug 5, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@danielroe danielroe danielroe approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@Hebilicious @danielroe
0