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 #39

Merged
merged 2 commits 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

Updated formatting for the GitHub workflow license comment.

📊 Key Changes

  • Adjusted the formatting of the license comment in the .github/workflows/format.yml file for clarity and style.

🎯 Purpose & Impact

  • 🛠️ Purpose: Ensures consistent and polished formatting across project files.
  • 🌟 Impact: Enhances readability and professionalism of the workflow configuration, though it doesn't affect functionality.

@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 an ultralytics/wave 🚀 PR! To ensure a seamless integration of your work, please review the following checklist:

  • Define a Purpose: Clearly explain the purpose of your update 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 that your PR is synchronized with the ultralytics/wave 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 that all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues accordingly.
  • Update Documentation: Ensure any relevant documentation has been updated to reflect your changes.
  • Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
  • Sign the CLA: If this is your first PR, please make sure to sign the Contributor License Agreement (CLA) by adding a comment saying, "I have read the CLA Document and I sign the CLA."
  • Minimize Changes: Keep your changes focused on addressing the issue described in your PR, limiting them to the minimum necessary for this update. As Bruce Lee wisely said: "It is not daily increase but daily decrease, hack away the unessential." 🌿

For more guidance, please refer to our Contributing Guide. If this PR is a bug fix, and you haven’t already, please include a minimum reproducible example (MRE) to help us verify and validate this update. 🔬

Thank you for your contribution to Ultralytics! 🌟 One of our engineers will review and provide feedback on your PR shortly. Please feel free to reach out if you have any questions in the meantime! 🚀

@pderrenger pderrenger merged commit bda421e into main Jan 15, 2025
2 checks passed
@pderrenger pderrenger deleted the refactor-20250115173012 branch January 15, 2025 16:32
@UltralyticsAssistant
Copy link
Member

🎉 Congratulations, @pderrenger, your PR has been merged! Huge thanks to you and @glenn-jocher for refining the workflow formatting – it’s the small details, like this, that elevate a project from functional to exceptional. 👏

As Leonardo da Vinci once said, "Details make perfection, and perfection is not a detail." Your thoughtful adjustments contribute to the clarity and professionalism that set this project apart. Thank you for your dedication—it truly makes a difference! 🚀💡

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