Ultralytics Refactor https://ultralytics.com/actions

[pderrenger]

This Ultralytics PR refactors code to improve performance and readability. 🔄

Key changes include:

• 🚀 Optimized various functions for faster execution.
• 🧩 Simplified complex logic for better understanding and maintenance.
• 🗑️ Removed redundant code to streamline operations.
• 📚 Improved code structure and organization.

These changes aim to enhance the overall quality and efficiency of the code. 🌟

Learn more about Ultralytics:

• About Us 🌐
• Install the Ultralytics App 📲
• Read Our Blog 📝
• Learn about YOLO 🤖
• Explore Ultralytics HUB 🚀
• Check Out Our Plans 💼
• Join our Team 🌾
• AI in Healthcare 🏥
• AI in Manufacturing 🏭
• Attend YOLO VISION 2024 📅

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Minor polish to docs and workflow, plus a clearer, more reliable model initialization path for YOLOE-11s when no classes are provided. ✅

📊 Key Changes

• 🔧 Predict: Refactored re_init_model logic so the prompt-free YOLOE-11s model loads by default when no class names are given; added clarifying comments.
• 📚 Docs: Updated Replicate API token link to a sign-in URL that reliably redirects to token generation.
• 🧹 CI: Tidied spacing in the GitHub Actions model matrix for readability (no behavior change).

🎯 Purpose & Impact

• 🎯 More predictable behavior: Ensures the prompt-free YOLOE-11s model is used when users don’t specify classes, while preserving the class-conditioned path when they do.
• 🚀 Smoother onboarding: The new token link reduces friction for first-time setup on Replicate.
• 🛡️ No breaking changes: Inference remains the same for users providing classes; CI is unaffected.

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting an ultralytics/replicate 🚀 PR! This is an automated response — an Ultralytics engineer will also review and assist you shortly. To ensure a seamless integration of your work, please review the following checklist:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/replicate main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

Quick note on your changes:

• yoloe11s/predict.py: Thanks for improving clarity around class-name handling and defaulting to the prompt-free YOLOE-11s when appropriate. Please confirm behavior for edge cases like mixed whitespace and trailing commas to ensure consistency.
• README.md: Appreciated the Replicate token link update to the sign-in flow for smoother onboarding.
• .github/workflows/push.yml: Matrix formatting cleanup looks good and non-functional.

For more guidance, please refer to our Contributing Guide. Don’t hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀