Accept normalized CLA signature comments

[glenn-jocher]

Valid CLA signature comments with trailing whitespace or surrounding Markdown currently never reach the normalized action matcher because the workflow gate requires exact equality.

This makes only the signature gate permissive. The recheck command remains exact, and the action still decides whether a single normalized line is a valid signature, so quoted or instructional text does not sign the CLA.

Related matcher fix: ultralytics/actions#894

Validation:

• actionlint .github/workflows/cla.yml
• npx prettier@3.8.5 --check .github/workflows/cla.yml

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Updated the CLA workflow gate to recognize comments containing the normalized CLA signature text, allowing trailing whitespace or surrounding Markdown to reach the action matcher.

📊 Key Changes

• Replaced the exact CLA signature comparison in .github/workflows/cla.yml with a contains(...) check.
• Kept the recheck command comparison exact.
• Preserved validation by the action’s normalized single-line matcher, so surrounding quoted or instructional text does not independently sign the CLA.

🎯 Purpose & Impact

• CLA signature comments with formatting or trailing whitespace can now be processed by the action instead of being blocked by the workflow condition.
• The change is limited to the signature gate; recheck behavior remains unchanged.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/replicate 🚀 PR! This automated message confirms your contribution was received, and an Ultralytics engineer will assist with the review. To ensure a seamless integration of your work, please review the following checklist:

• ✅ 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/replicate 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}

LGTM. The change is scoped to the CLA signature workflow gate, allowing comments containing the valid signature text to reach the action matcher while preserving the exact recheck command behavior. No concrete regression is evident in the reviewed diff.

[UltralyticsAssistant]

🎉 PR #49 was merged—thank you, @glenn-jocher!

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

This focused update improves CLA signature handling by allowing formatted comments and trailing whitespace to reach the action’s normalized matcher, while preserving exact recheck behavior and validation against unintended surrounding text.