Skip to content

Add CLA workflow - #94

Merged
glenn-jocher merged 4 commits into
mainfrom
add-cla-workflow
Jul 9, 2026
Merged

Add CLA workflow#94
glenn-jocher merged 4 commits into
mainfrom
add-cla-workflow

Conversation

@glenn-jocher

@glenn-jocher glenn-jocher commented Jul 9, 2026

Copy link
Copy Markdown
Member

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) workflow to manage contributor sign-offs on pull requests. 🤝

📊 Key Changes

  • Added .github/workflows/cla.yml to:
    • Run when pull requests are opened, reopened, or updated.
    • Allow CLA rechecks through issue comments.
    • Automatically request contributors to sign the Ultralytics CLA.
  • Uses the shared ultralytics/actions/cla@main action.
  • Configured permissions for pull request and workflow action updates.
  • Added concurrency controls to prevent duplicate CLA checks for the same pull request.

🎯 Purpose & Impact

  • Ensures contributors complete the required CLA before their changes can be merged. ✅
  • Automates compliance checks, reducing manual maintainer effort.
  • Provides a consistent contribution process across repositories.
  • Gives contributors a clear way to recheck or confirm their CLA status through comments.

@UltralyticsAssistant UltralyticsAssistant added the devops GitHub Devops or MLops label Jul 9, 2026
@UltralyticsAssistant

Copy link
Copy Markdown
Member

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/template 🚀 PR! This automated checklist helps ensure a seamless integration, and an engineer will assist if you have 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/template 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! 🚀

@codecov

codecov Bot commented Jul 9, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@UltralyticsAssistant UltralyticsAssistant left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔍 PR Review

Made with ❤️ by Ultralytics Actions

The workflow triggers and permission scopes otherwise match the action's required PR-comment and workflow-rerun operations. However, the pinned CLA action revision can overwrite unrelated GitHub Actions bot comments.

💬 Posted 1 inline comment

Comment thread .github/workflows/cla.yml Outdated
@glenn-jocher
glenn-jocher merged commit f4167ea into main Jul 9, 2026
14 checks passed
@glenn-jocher
glenn-jocher deleted the add-cla-workflow branch July 9, 2026 23:39
@UltralyticsAssistant

Copy link
Copy Markdown
Member

🎉 Thank you, @glenn-jocher, for this valuable contribution—and congratulations on the merge!

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

By adding an automated CLA workflow, this PR strengthens the contributor experience, streamlines compliance checks, and helps maintain a consistent, welcoming contribution process across Ultralytics repositories. Your work makes collaboration easier for everyone! 🤝

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

devops GitHub Devops or MLops

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants