Update CLA.md

[abhilipsasahoo03]

Signed-off-by: Abhilipsa Sahoo abhilipsasahoo03@gmail.com

Description

Enhanced readability of CLA.md file to make it more comprehensible for new contributors.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: abhilipsasahoo03 / name: Abhilipsa Sahoo (5bc32c8)

[k8s-ci-robot]

Welcome @abhilipsasahoo03!

It looks like this is your first PR to kubernetes/community 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/community has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @abhilipsasahoo03. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[cpanato]

thanks for your PR
a few comments
/ok-to-test

[abhilipsasahoo03]

@mrbobbytables @cpanato I have undone the changes that felt unnecessary in this case, as per your reviews. Please take a look and let me know if anything else is required.

[mrbobbytables]

Thanks!
One last thing - Can you please squash/fixup the commits and remove the merge commit?

[abhilipsasahoo03]

Thanks!
One last thing - Can you please squash/fixup the commits and remove the merge commit?

Hi can I squash through GitHub automation or do I have to do it manually? @mrbobbytables

[mrbobbytables]

Preferred is fixup manually to remove the merge commit and remove the additional commit messages. Squashing Rolls up all the messages into the top level commit message. Fixup removes the unnecessary commit messages.

[abhilipsasahoo03]

/label tide/merge-method-squash

[abhilipsasahoo03]

Preferred is fixup manually to remove the merge commit and remove the additional commit messages. Squashing Rolls up all the messages into the top level commit message. Fixup removes the unnecessary commit messages.

I would have done manually but I had to delete my local copy due to some issues. What happens if I do it via automation? @mrbobbytables

[mrbobbytables]

I would have done manually but I had to delete my local copy due to some issues. What happens if I do it via automation?

The automation treats it like a full squash. All commit messages are preserved and rolled up into the final commit message. The automation makes it convenient at the cost of a quality commit message.

While it'd probably be okay here, its not something we encourage where commit history is important.

[jberkus]

Given that the commit history isn't that important for this merge, approving.

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhilipsasahoo03, jberkus

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jberkus]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment