If you are trying to sign the CLA so your PR’s can be merged, please read the CLA docs
If you are a Kubernetes GitHub organization or repo owner, and would like to setup the Linux Foundation CNCF CLA check for your repositories, please read on.
group=284specifies the ID of the CNCF project authorized committers group in our CLA system.
comment=nospecifies that our system should not post help comments into the pull request (since the Kubernetes mungebot does this).
target=https://identity.linuxfoundation.org/projects/cncfspecifies what will be used for the “Details” link in GitHub for this status check.
It is recommended that the Linux Foundation CLA check be added as a strict requirement for any change to be accepted to the master branch.
To do this manually:
Given the Kubernetes projects anticipates having “human reviewed” CLA acceptance, you may not do the last step, but it is still recommended to enable branch protection to require all changes to be done through pull requests, instead of direct pushing that will never kick off a CLA check.
You also need to add @k8s-ci-robot as one of the owners in
the same org/repo, to ensure that it can add labels
cncf-cla: yes and
cncf-cla: no based
on the status published by the Linux Foundation webhook.
The label automation may not be essential for your repository, if you’re not using merge automation. For repos with maintainers doing manual merges, GitHub protected branches may suffice.