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 pass comments containing the normalized signature phrase to the existing matcher, allowing trailing whitespace or surrounding Markdown to be handled.

📊 Key Changes

• Replaced exact equality for CLA signature comments with a contains() check in .github/workflows/cla.yml.
• Kept the recheck command matching exact.
• Left final signature validation to the existing action matcher, which evaluates the normalized comment content.

🎯 Purpose & Impact

• CLA comments with surrounding Markdown or trailing whitespace can now reach the signature validation step instead of being rejected by the workflow gate.
• The workflow does not treat every matching comment as a valid signature; the action still performs the final normalized-line check.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/kinect 🚀 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/kinect 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 workflow now triggers the CLA action for signature comments containing surrounding Markdown or trailing whitespace, while the action remains responsible for validating an exact normalized signature line. The recheck command remains exact, and no repository-local correctness or security regression is evident.

[UltralyticsAssistant]

🎉 PR #35 has been merged—thank you, @glenn-jocher!

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

This focused workflow improvement lets CLA comments with surrounding Markdown or trailing whitespace reach the existing normalized signature matcher, while keeping recheck matching exact and final validation unchanged.