@camilamacedo86 reviewed, looks good 😄

I would add comment-spacings in linters-settings.revive.rules of .golangci.yml to enforce this in the future. Adding it in top of this PR gets only this 2 errors

pkg/rescaffold/migrate.go:333:2: comment-spacings: no space between comment delimiter and comment text (revive)
	//Copy all the contents to the desitination file
	^
pkg/cli/alpha.go:38:3: comment-spacings: no space between comment delimiter and comment text (revive)
		//TODO: If we need to create alpha commands please add a new file for each command
		^

(so the primary problem was fixed!)

If you need help fixing the CI, I can take a look

Hi @mateusoliveira43

#3904 (comment)
That we can do in a follow up after this one get merged.

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

Hey @camilamacedo86 - this looks good! Just curious, looks like the space has been introduced in all the places? Is it necessary because iirc c-t does not parse both the cases ?

I think it might be a convention because the user that raised it out complains about some lints checks that raise issues related to it see:

cmd/main.go:52:2: comment-spacings: no space between comment delimiter and comment text (revive)
	//+kubebuilder:scaffold:scheme
	^

However, my main motivation is make it easier for users. It is hard to know what marker should have space or not so since all places has space lets keep the space. That was my thought.

New changes are detected. LGTM label has been removed.

I also checked that controller-runtime either is using space for all marker comments , https://github.com/search?q=repo%3Akubernetes-sigs%2Fcontroller-runtime++%22%2F%2F+%2B%22&type=code so that seems the right way to move forward.