Skip to content

Add yolo26 tasks banner#162

Closed
raimbekovm wants to merge 2 commits into
mainfrom
docs/add-yolo26-tasks-banner
Closed

Add yolo26 tasks banner#162
raimbekovm wants to merge 2 commits into
mainfrom
docs/add-yolo26-tasks-banner

Conversation

@raimbekovm
Copy link
Copy Markdown
Member

@raimbekovm raimbekovm commented May 20, 2026

summary

adds the new yolo26 tasks banner (7 tasks: detect, segment, semantic, classify, pose, obb, track — previously 6). served as image/avif via raw github and jsdelivr, used by ultralytics/ultralytics readme and docs.

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

This PR appears to update repository assets, but the provided diff does not include the actual code or content changes, so only a limited summary is possible. 🖼️

📊 Key Changes

  • An asset file was modified: docs/ultralytics-yolov8-tasks-banner.avif.
  • The changed file is an image/banner asset, likely related to documentation or visual branding.
  • No source diff or content preview was provided, so there are no visible code, logic, or API changes to summarize. ℹ️

🎯 Purpose & Impact

  • Likely refreshes or improves documentation visuals for a better user experience 📚
  • May update branding, layout, or promotional imagery shown in docs or related pages 🎨
  • Should have little to no impact on functionality, training, inference, or developer workflows ✅
  • Since the actual diff is not included, any deeper assessment of user-facing impact would be speculative 🔍
📋 Skipped 1 file (lock files, generated, images, etc.)
  • docs/ultralytics-yolov8-tasks-banner.avif

@UltralyticsAssistant UltralyticsAssistant added documentation Improvements or additions to documentation enhancement New feature or request priority: low Low urgency; can wait behind higher-priority work. labels May 20, 2026
@UltralyticsAssistant
Copy link
Copy Markdown
Member

👋 Hello @raimbekovm, thank you for submitting a ultralytics/assets 🚀 PR! This is an automated message to help streamline review, and an engineer will assist you soon. Please review the checklist below for a smooth integration ✨

  • 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/assets 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

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! 🚀

Copy link
Copy Markdown
Member

@UltralyticsAssistant UltralyticsAssistant left a comment

Choose a reason for hiding this comment

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

🔍 PR Review

Made with ❤️ by Ultralytics Actions

All 1 changed files are generated/vendored (skipped review)

📋 Skipped 1 file (lock files, generated, images, etc.)
  • docs/ultralytics-yolo26-tasks-banner.avif

@raimbekovm raimbekovm closed this May 20, 2026
@raimbekovm raimbekovm deleted the docs/add-yolo26-tasks-banner branch May 20, 2026 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation enhancement New feature or request priority: low Low urgency; can wait behind higher-priority work.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants