Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize license headers in TOML/YAML files #20

Merged
merged 1 commit into from
Jan 15, 2025

Conversation

pderrenger
Copy link
Member

@pderrenger pderrenger commented Jan 15, 2025

This PR updates all YAML file headers to use a standardized license format. 🔄

Changes:

  • 📝 Standardized header: # Ultralytics 🚀 AGPL-3.0 License - https://ultralytics.com/license
  • 🧹 Ensures consistent spacing after headers
  • 🔍 Applies to all YAML files except those in venv

Learn more about Ultralytics licensing 📚

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

Improved code formatting workflow by refining license header syntax in the configuration.

📊 Key Changes

  • Updated the license header in the format.yml workflow file to restructure and clarify its formatting.

🎯 Purpose & Impact

  • 🎯 Purpose: Enhances code clarity and professionalism in workflow files.
  • 📈 Impact: Makes license details more readable and accessible, improving maintainability and comprehension for contributors.

@UltralyticsAssistant UltralyticsAssistant added devops GitHub Devops or MLops documentation Improvements or additions to documentation labels Jan 15, 2025
@UltralyticsAssistant
Copy link
Member

👋 Hello @pderrenger, thank you for submitting your ultralytics/ntc 🚀 PR! To ensure a smooth review and integration process, please take a moment to review the following checklist:

  • Define a Purpose: Clearly explain the purpose of your PR and include links to any relevant issues. Make sure your commit messages are clear and follow project conventions.
  • Synchronize with Source: Confirm your branch is up-to-date with the main branch of ultralytics/ntc. If it is not, please click ‘Update branch’ or run git pull and git merge main locally to ensure your PR is up-to-date.
  • Ensure CI Checks Pass: Verify that all Ultralytics Continuous Integration (CI) checks pass. If any checks fail, kindly investigate and resolve the issues before requesting a review.
  • Update Documentation: If your changes introduce or modify a feature, please make sure to update the documentation accordingly.
  • Add Tests: If applicable, include tests or update existing ones to validate your changes, and ensure that all tests pass successfully.
  • Sign the CLA: If this is your first contribution to Ultralytics, please ensure you have signed our Contributor License Agreement (CLA). To do this, comment "I have read the CLA Document and I sign the CLA" in this PR.
  • Minimize Changes: Please ensure your changes are minimal, focused, and directly address the purpose of this PR. As Bruce Lee said, "It is not daily increase but daily decrease, hack away the unessential."

For additional guidance, please review our Contributing Guide. Feel free to leave a comment here if you have questions or require assistance. An Ultralytics engineer will review and help out soon. Thank you for contributing and helping improve the Ultralytics ecosystem! 🚀🔧

@pderrenger pderrenger merged commit 5ea349b into main Jan 15, 2025
1 check passed
@pderrenger pderrenger deleted the refactor-20250115173012 branch January 15, 2025 16:33
@UltralyticsAssistant
Copy link
Member

🎉 This PR has officially been merged—amazing teamwork, @pderrenger and @glenn-jocher!

Your careful update to the license header isn’t just about formatting; it’s about creating clarity and fostering professionalism that uplifts the entire project. As Leonardo da Vinci once said, "Simplicity is the ultimate sophistication." Your contributions embody this philosophy, making the workflows sharper and more accessible for everyone.

Thank you for your dedication and for helping us all move forward, one meaningful improvement at a time! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops GitHub Devops or MLops documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants