Excessive REST API calls in PR Review

[glenn-jocher]

Let's swap for GraphQL to reduce calls.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/actions 🚀 Issue. This is an automated response to help gather the right details quickly — an Ultralytics engineer will follow up with you soon 🤖

To help us address your concern about REST API calls vs. GraphQL in PR review efficiently, please ensure you've provided the following information:

1. For bug reports:

   • A clear and concise description of the bug
   • A minimum reproducible example MRE that demonstrates the issue
   • Your environment details (OS, Python version, package versions)
   • Expected behavior vs. actual behavior
   • Any error messages or logs related to the issue

2. For feature requests:

   • A clear and concise description of the proposed feature (for example, swapping REST for GraphQL in specific steps of the PR review workflow)
   • The problem this feature would solve (such as rate limits, latency, or excessive calls)
   • Any alternative solutions you've considered or tried

3. For questions:

   • Provide as much context as possible about your question
   • Include any research you've already done on the topic
   • Specify which parts of the documentation, if any, you've already consulted

Please also confirm whether this is primarily:

• A performance/optimization request
• A reliability/rate-limiting issue
• Or a general architectural suggestion

And if you have any logs, metrics, or sample PR workflows that illustrate the current behavior, adding those will be very helpful 📊

Please make sure you've searched existing issues to avoid duplicates. If you need to add any additional information, please comment on this issue.