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 to pass comments containing the standard CLA signature text to the normalized signature matcher, while keeping recheck matching exact.

📊 Key Changes

• Replaced exact equality for CLA signature comments with contains(...) in .github/workflows/cla.yml.
• Comments with surrounding whitespace or Markdown can now reach the action’s normalized signature validation.
• The recheck command still requires an exact comment match.
• The action continues to determine whether the normalized comment is a valid single-line signature.

🎯 Purpose & Impact

• CLA comments that include formatting around the recognized signature can now be evaluated instead of being rejected by the workflow gate; quoted or instructional text is not automatically treated as a signature.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/wave 🚀 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/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 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]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/wave 🚀 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/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 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}

Reviewed the complete .github/workflows/cla.yml diff and surrounding workflow behavior. The change is scoped to the signature trigger, preserves exact recheck handling, and does not create a CLA-signing bypass because signature validation remains owned by the action. LGTM.

[UltralyticsAssistant]

🎉 PR #52 has been merged—thank you, @glenn-jocher, for the contribution!

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

This update makes CLA comments with surrounding whitespace or Markdown eligible for normalized signature validation, while keeping recheck matching exact.