fix(workflow): fix branch name

[derekbit]

Which issue(s) this PR fixes:

Issue longhorn/longhorn#10193

What this PR does / why we need it:

Special notes for your reviewer:

Additional documentation or context

[coderabbitai]

Walkthrough

The pull request modifies the GitHub Actions workflow file for creating CRD update pull requests in the Longhorn repository. The primary change is switching the authentication token from a custom GitHub token to the default GITHUB_TOKEN. Additionally, the branch naming convention for the pull request has been updated. The overall workflow structure and functionality remain consistent with the previous implementation.

Changes

File	Change Summary
.github/workflows/create-crd-update-pr-in-longhorn-repo.yml	Token updated from ${{ secrets.CUSTOM_GITHUB_TOKEN }} to ${{ secrets.GITHUB_TOKEN }}; Branch name updated from "update-image-tags-${{ inputs.branch }}" to "update-crds-and-manifests-longhorn-manager-${{ github.event.pull_request.number }}"

Assessment against linked issues

Objective	Addressed	Explanation
Automatically create PR for patching CRDs and manifests [#10193]	✅
Simplify CRD and manifest update process	✅

The changes align with the original issue's objectives by maintaining the automated PR creation workflow for updating CRDs and manifests. The token change does not impact the core functionality of automatically generating and potentially merging the pull request.

Possibly related PRs

• chore(k8s): auto-patch namespace and labels while regenerating crds.yaml #3486: The changes in this PR involve updates to the k8s/crds.yaml file, which is relevant to the workflow changes in the main PR that also deals with CRDs and manifests in the Longhorn repository.

Suggested reviewers

• innobead
• mantissahz
• COLDTURNIP

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 857e21b and 9ef2333.

📒 Files selected for processing (1)

• .github/workflows/create-crd-update-pr-in-longhorn-repo.yml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/create-crd-update-pr-in-longhorn-repo.yml

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Build binaries
• GitHub Check: Summary

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ea0a417 and 857e21b.

📒 Files selected for processing (1)

• .github/workflows/create-crd-update-pr-in-longhorn-repo.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Build binaries
• GitHub Check: Summary