[slowroll] Add openSUSE Slowroll support

[goldyfruit]

Implement #118

Summary by CodeRabbit

• New Features

  • Added support for "openSUSE Slowroll" in the documentation, enhancing clarity on supported systems.
  • Expanded the required_packages function to include package installation support for the "openSUSE Slowroll" distribution.

• Tests

  • Introduced two new test cases for handling the "openSUSE Slowroll" distribution in the test suite, improving test coverage.

[coderabbitai]

Walkthrough

The recent changes enhance support for the "openSUSE Slowroll" distribution across various files. Updates in the README.md improve documentation clarity, while the BATS test suite now includes scenarios validating the required_packages function for this distribution. The utils/common.sh file has been updated to integrate "openSUSE Slowroll" into its package management logic, ensuring that users can install necessary packages seamlessly.

Changes

File	Change Summary
README.md	Added support entry for "openSUSE Slowroll" with version "rolling" in the systems table.
tests/bats/packages.bats	Introduced two tests for required_packages: one for success and one for failure in "opensuse-slowroll."
utils/common.sh	Modified required_packages function to include conditional logic for "opensuse-slowroll."

Poem

In the meadow green and bright,
A rabbit hops with pure delight.
"OpenSUSE Slowroll," hear the cheer,
Packages now, with joy, appear! 🐇✨
With tests and code, our world expands,
Together, we build with gentle hands!

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5b090a1 and dc3fc04.

Files selected for processing (3)

• README.md (1 hunks)
• tests/bats/packages.bats (2 hunks)
• utils/common.sh (1 hunks)

Files skipped from review due to trivial changes (1)

• README.md

Additional comments not posted (3)

tests/bats/packages.bats (2)

115-122: LGTM!

The test case for opensuse-slowroll is correctly implemented and follows the existing pattern for other distributions.

---

241-248: LGTM!

The failure test case for opensuse-slowroll is correctly implemented and follows the existing pattern for other distributions.

utils/common.sh (1)

219-219: LGTM!

The inclusion of opensuse-slowroll in the required_packages function is correctly implemented and follows the existing pattern for other distributions.