AE for cloud, add description for vendor

[EvilOlaf]

Description

As per title

How Has This Been Tested?

• hasn't

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[coderabbitai]

Walkthrough

This change updates the fallback descriptions for kernel branch options within the interactive_config_ask_branch function in interactive.sh. The description for the "legacy" branch is modified to remove the word "Vendor," and the "cloud" branch description is updated to use American English spelling. Additionally, a new "vendor" kernel branch option is introduced with its own description. No changes are made to the logic or control flow, and no exported or public entity declarations are altered.

Possibly related PRs

• Proposed Change - Add Kernel Version Parsing and Custom Description #8152: The main PR modifies static kernel branch descriptions and adds a new "vendor" branch option in interactive_config_ask_branch(), while the retrieved PR introduces dynamic kernel description parsing and display from family config files and refactors interactive_config_ask_branch() to use this dynamic data, making the changes in the main PR related to the description handling enhancements introduced in the retrieved PR.

Suggested labels

ready to merge

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b21758c and 76dbb0d.

📒 Files selected for processing (1)

• lib/functions/configuration/interactive.sh (1 hunks)

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

• lib/functions/configuration/interactive.sh

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Commit Unit Tests in branch kernel-description
• Post Copyable Unit Tests in Comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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: 1

🧹 Nitpick comments (1)

lib/functions/configuration/interactive.sh (1)

236-236: Legacy branch description: redundant slash before “kernel”
The updated description Old stable / Legacy / kernel leaves an extra slash. Consider merging “Legacy” and “kernel” for clarity.

Apply this diff:

-    description="Old stable / Legacy / kernel"
+    description="Old stable / Legacy kernel"

🧰 Tools

🪛 GitHub Actions: Shellcheck - PR #8299 ("AE for cloud, add description for vendor")

[error] ShellCheck detected critical errors in lib/ code causing the pipeline to fail with exit code 1.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bc6e97c and b21758c.

📒 Files selected for processing (1)

• lib/functions/configuration/interactive.sh (1 hunks)

🧰 Additional context used

🪛 Shellcheck (0.10.0)

lib/functions/configuration/interactive.sh

[error] 244-244: Couldn't parse this case item. Fix to allow more checks.

(SC1073)

🪛 GitHub Actions: Shellcheck - PR #8299 ("AE for cloud, add description for vendor")

lib/functions/configuration/interactive.sh

[error] ShellCheck detected critical errors in lib/ code causing the pipeline to fail with exit code 1.

🔇 Additional comments (1)

lib/functions/configuration/interactive.sh (1)

242-242: Cloud branch description uses correct American spelling
The change from “optimised” to “optimized” aligns with US English conventions.

🧰 Tools

🪛 GitHub Actions: Shellcheck - PR #8299 ("AE for cloud, add description for vendor")

[error] ShellCheck detected critical errors in lib/ code causing the pipeline to fail with exit code 1.