Add Permissions to Ultralytics Actions format.yml

[glenn-jocher]

This pull request significantly enhances the Ultralytics Actions workflow, introducing permissions for security best practices, alongside intelligent issue and PR handling. This includes automatic labeling, spam detection, abuse identification, and off-topic filtering. These updates ensure a more efficient and organized workflow, adhering to the latest Ultralytics standards.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Improved GitHub workflow automation and made minor formatting updates to scoring scripts for better consistency and maintainability. 🚀✨

📊 Key Changes

• Enhanced the GitHub Actions workflow:
  • Added clearer permissions for modifying code, PRs, and issues.
  • Updated action steps for improved code formatting, auto-labeling, spell checking, and AI-powered PR summaries.
  • Integrated support for additional API keys (OpenAI and Brave) to enable advanced features.
• Added a blank line after the license header in several scoring scripts for consistent formatting.

🎯 Purpose & Impact

• 🛠️ Streamlines code review and maintenance by automating formatting, labeling, and summary generation.
• 🤖 Leverages AI to provide better PR summaries and labeling, saving developer time.
• 📄 Improves code readability and consistency, making collaboration easier for all contributors.
• 🔒 Ensures proper permissions are set for safer and more effective workflow automation.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting an ultralytics/xview-yolov3 🚀 PR! This is an automated response to help guide your contribution—an Ultralytics engineer will review and assist soon.

Please review the following checklist to ensure a smooth integration:

• ✅ Define a Purpose: Clearly state the purpose of your fix or feature in the PR description, and link to any relevant issues. Commit messages should be clear and follow project conventions.
• ✅ Synchronize with Source: Ensure your PR is up to date with the main branch of ultralytics/xview-yolov3. If needed, click the 'Update branch' button or use git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: All Ultralytics Continuous Integration (CI) checks should pass. Please address any failures.
• ✅ Update Documentation: Update documentation for any new or changed features.
• ✅ Add Tests: Where applicable, include or update tests to cover your changes and confirm all tests pass.
• ✅ Sign the CLA: If this is your first Ultralytics PR, sign our Contributor License Agreement (CLA) by commenting: "I have read the CLA Document and I sign the CLA".
• ✅ Minimize Changes: Limit your changes to the minimum required for your fix or feature. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more details, see our Contributing Guide. If you have any questions, feel free to comment below. Thank you for helping improve Ultralytics! 🚀🤖

[UltralyticsAssistant]

Fantastic work, @glenn-jocher! 🚀 Your improvements to the GitHub workflow and scoring scripts are a big step forward for project consistency and automation. As Henry Ford said, “Coming together is a beginning; keeping together is progress; working together is success.” Your efforts embody this spirit—making collaboration smoother and more efficient for everyone. Thank you for continually pushing the boundaries and elevating the Ultralytics community!