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 an automated Contributor License Agreement (CLA) check to the repository’s GitHub workflows. 🤝

📊 Key Changes

• Adds a new .github/workflows/cla.yml workflow.
• Runs CLA checks when pull requests are opened, reopened, or updated.
• Allows contributors to trigger a recheck by commenting recheck or confirming CLA acceptance.
• Uses the shared ultralytics/actions/cla action to manage verification.
• Grants the workflow permissions to update actions and pull requests.

🎯 Purpose & Impact

• Ensures contributors complete the Ultralytics CLA before their pull requests can be merged. ✅
• Automates compliance checks and reduces manual maintainer work.
• Provides a clear process for contributors to sign or recheck the CLA.
• Improves consistency and governance for future contributions without changing the project’s runtime code. 🚀

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/mobileclip 🚀 PR! This automated checklist helps keep the contribution process smooth, and an engineer will assist with any questions or follow-up:

• ✅ 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/mobileclip 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]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

Clean PR. The workflow matches the pinned Ultralytics CLA action’s documented trigger, permission, token, and recheck configuration, while safely limiting execution to this repository and PR issue comments.

[UltralyticsAssistant]

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

“Great things are done by a series of small things brought together.” — Vincent van Gogh

This PR streamlines CLA verification, makes rechecks easier for contributors, and reduces manual maintenance while supporting a clearer, more consistent path for future contributions. 🤝