📖 Simplify if condition in cronjob tutorial

[lpugoy]

In the "Writing tests" section of the cronjob tutorial, the following code

if err != nil {
	return false
}
return true

can be simplified to

return err == nil

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: lpugoy (f8c472b)

[k8s-ci-robot]

Welcome @lpugoy!

It looks like this is your first PR to kubernetes-sigs/kubebuilder 🎉. 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-sigs/kubebuilder 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 @lpugoy. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

[camilamacedo86]

Hi @lpugoy

When we do changes we need to run make generate
(you can check the Makefile and the Contributing.md guide)

Make generate will re-generated the docs and samples under the testdata dir.
Therefore, this changes must be done in the logic that we use to update it. That means, here: https://github.com/kubernetes-sigs/kubebuilder/tree/master/hack/docs/internal/cronjob-tutorial

So, can you please:

• Update the hack/docs with your change
• Run make generate
• Squash the commits and push it

So, that we can get it merged.

Thank you 🥇

[lpugoy]

Sorry for that @camilamacedo86. I have fixed the changes and run make generate.

The Contributing.md guide also mentioned that I should submit an issue. Should I do that as well?

[camilamacedo86]

/lgtm

/approved

[camilamacedo86]

Hi @lpugoy

Sorry for that @camilamacedo86. I have fixed the changes and run make generate.
The Contributing.md guide also mentioned that I should submit an issue. Should I do that as well?

Thank you and all fine.
You do not need to open an issue for it.
It is too small.

However, see that it is falling because your branch is not rebased with master.
Could you please rebase with the master so that we can get this one merged?

[camilamacedo86]

/ok-to-test
/lgtm
/approved

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, lpugoy

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 [camilamacedo86]

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

[lpugoy]

Thank you for your patience @camilamacedo86 .

[camilamacedo86]

hi @lpugoy
Thank you for the contribution