✨ feat(alpha/update): add git commands to GH issue description

[vitorfloriano]

The issue created by alpha update now contains git commands to facilitate checking out the branch generated by the alpha update command when there are merge conflicts.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vitorfloriano
Once this PR has been reviewed and has the lgtm label, please assign varshaprasad96 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

@vitorfloriano: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubebuilder-test	70ee229	link	true	/test pull-kubebuilder-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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-sigs/prow repository. I understand the commands that are listed here.

[camilamacedo86]

We need to share something like If you want to run this update manually then use alpha update.
WDYT?

[vitorfloriano]

If the workflow has already created the updated branch, is it still necessary to run alpha update locally?

Then we would also need to inform users that they need to install the latest binary to do that...

I was also thinking about adding a link to the workflow that created the issue, so users can inspect the logs and understand what happened.

It could be something like this:

---

Description

Upgrade your project to use the latest scaffold changes introduced in Kubebuilder %[1]s.

See the release notes from %[3]s to %[1]s for details about the changes included in this upgrade.

What to do

A scheduled workflow already attempted this upgrade and created the branch (%[4]s) to help you in this process. You can see the logs from the workflow run in here: %[6]s 👈 ADD THIS

⚠️ Conflicts were detected during the merge.

Create a Pull Request using the URL below to review the changes and resolve conflicts manually:
%[2]s 👈 REMOVE THIS

Next steps

1. Fetch the %[4]s branch locally:

git fetch https://github.com/%[5]s %[4]s:%[4]s
git checkout %[4]s

2. Locate and resolve the merge conflicts.

3. After fixing conflicts, run:

make manifests generate fmt vet lint-fix

4. Verify the changes:

• Build the project
• Run tests
• Confirm everything still works

Optional

If you wish to run this migration locally, please refer to the docs: 👈 ADD THIS TOO

📖 https://kubebuilder.io/reference/commands/alpha_update

---

WDYT?

[k8s-ci-robot]

PR needs rebase.

Details

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-sigs/prow repository.