Skip to content

Update README.md#69

Merged
glenn-jocher merged 1 commit intomainfrom
glenn-jocher-patch-1
Jul 3, 2025
Merged

Update README.md#69
glenn-jocher merged 1 commit intomainfrom
glenn-jocher-patch-1

Conversation

@glenn-jocher
Copy link
Copy Markdown
Member

@glenn-jocher glenn-jocher commented Jul 3, 2025

@pderrenger updated with license mention.

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

Added information about Ultralytics' enterprise licensing options to the GitHub profile README. 🏢✨

📊 Key Changes

🎯 Purpose & Impact

  • Informs users about available enterprise licensing, making it easier for businesses to find commercial solutions.
  • Enhances transparency and helps organizations understand their options for using Ultralytics technology in commercial projects.

@pderrenger updated with license mention.

Signed-off-by: Glenn Jocher <glenn.jocher@ultralytics.com>
@UltralyticsAssistant UltralyticsAssistant added the documentation Improvements or additions to documentation label Jul 3, 2025
@UltralyticsAssistant
Copy link
Copy Markdown
Member

👋 Hello @glenn-jocher, thank you for submitting an ultralytics/.github 🚀 PR! To ensure a seamless integration of your updates, please review the following checklist:

  • Define a Purpose: Clearly explain the purpose of your update in the PR description, and link to any relevant issues if applicable. Make sure your commit messages are clear and follow project conventions.
  • Synchronize with Source: Confirm your PR is synchronized with the ultralytics/.github main branch. If it’s behind, update it by clicking the 'Update branch' button or running git pull and git merge main locally.
  • Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. Please address any issues if checks fail.
  • Update Documentation: Ensure all relevant documentation reflects your changes if applicable.
  • Add Tests: If your update would benefit from tests, please add or update them and confirm all tests are passing.
  • Sign the CLA: If this is your first Ultralytics PR, please sign our Contributor License Agreement by writing "I have read the CLA Document and I sign the CLA" in a new message.
  • Minimize Changes: Limit your update to the minimum necessary for this enhancement. "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, check our Contributing Guide. If you have any questions, feel free to comment here. This is an automated response — an Ultralytics engineer will also assist you soon. Thank you for helping improve Ultralytics! 🌟

@glenn-jocher glenn-jocher merged commit be1fdb0 into main Jul 3, 2025
3 checks passed
@glenn-jocher glenn-jocher deleted the glenn-jocher-patch-1 branch July 3, 2025 15:01
@UltralyticsAssistant
Copy link
Copy Markdown
Member

Fantastic work on this merge, @glenn-jocher! 🌟 As Thomas Edison said, "The value of an idea lies in the using of it." By clearly highlighting Ultralytics’ enterprise licensing options, you’re empowering more organizations to transform ideas into impactful solutions with confidence and clarity. Your dedication continues to make Ultralytics HUB a welcoming place for all users—thank you for driving transparency and growth!

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants