Add CLA workflow

[glenn-jocher]

Summary

• add the canonical public CLA workflow with the standard Ultralytics license header
• use ultralytics/actions/cla@main so repositories inherit shared fixes automatically
• route actionable events at the job boundary and grant only actions: write and pull-requests: write
• keep the ledger PAT isolated to the CLA step and central ultralytics/cla repository

Deleted: nothing. No CLA workflow or repository-local equivalent existed; organization-wide CLA enforcement cannot be achieved by deletion or relocation in this repository.

Reused: the canonical ultralytics/actions/.github/workflows/cla.yml structure and shared ultralytics/actions/cla@main implementation.

Validation

• byte-for-byte comparison with the reviewed ultralytics/actions/.github/workflows/cla.yml template
• actionlint .github/workflows/cla.yml
• npx prettier --write .github/workflows/cla.yml
• license-header, shared-main-action, and token-input scan
• git diff --check

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Adds automated Ultralytics Contributor License Agreement (CLA) checks to the repository’s pull request workflow. 🤝

📊 Key Changes

• Adds a new .github/workflows/cla.yml GitHub Actions workflow.
• Automatically checks CLA status when pull requests are opened, reopened, or updated.
• Allows contributors to trigger a CLA recheck by commenting recheck or confirming acceptance.
• Uses the shared ultralytics/actions/cla action with repository tokens.
• Grants the workflow permission to update pull requests and manage related actions.

🎯 Purpose & Impact

• Helps ensure contributors complete the required CLA before their changes are merged. ✅
• Reduces manual maintainer effort by automating CLA verification.
• Provides a consistent contribution process across the repository.
• May add a CLA status requirement that contributors must satisfy before PR approval or merge.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/msvm 🚀 PR! This automated checklist helps keep contributions moving smoothly, and an Ultralytics engineer will assist with any questions. Please review the following:

• ✅ 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/msvm 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! 🚀

[UltralyticsAssistant]

🎉 Merged—thank you, @glenn-jocher, for strengthening the repository’s contribution workflow with automated CLA checks!

As Helen Keller said, “Alone we can do so little; together we can do so much.” This PR helps make collaboration more consistent and efficient by simplifying CLA verification for every contributor. 🤝

Your work is greatly appreciated!