Turn the checkbox-lists of supported platforms and languages into normal bullet lists: Resolves #350

[syedalinaqihasni]

fixes #350

Problem:
The Supported Software Forges documentation section uses checkbox lists to indicate supported and unsupported platforms/languages. This design is ambiguous, especially for unchecked items—it's unclear whether they represent unsupported but recognized platforms, or something else entirely. This confusion weakens the clarity and usefulness of the documentation.

Solution:
Refactor the list formatting by:

• Removing all unchecked items from the list
• Replacing all checkbox-style list markers with standard bullet points
• Ensuring the list only reflects actively supported platforms/languages

Affected Components:

• Documentation: /finishing-touches/docstrings
• Markdown rendering of supported platforms and languages

Acceptance Criteria:

• All checkbox lists are replaced with bullet points
• Unchecked items are removed from the list
• Page clearly reflects only supported platforms/languages
• No ambiguity remains in list formatting or meaning

[coderabbitai]

Walkthrough

The documentation was updated to replace checkbox lists of supported software forges and languages with standard bullet points. Previously listed but unsupported options were removed. The explanatory text about Bitbucket support remains unchanged. No code or logic was altered; only documentation formatting and content were modified.

Changes

File(s)	Change Summary
docs/finishing-touches/docstrings.md	Replaced checkbox lists with bullet points; removed Bitbucket and unsupported languages from lists.

Assessment against linked issues

Objective	Addressed	Explanation
Remove unchecked items and replace checkboxes with bullets in supported lists (#350)	✅

Poem

In the docs, the boxes are gone,
Bullets now lead the lists along.
Bitbucket and Scala, we bid adieu,
Only what's supported, shining through.
A hop, a skip, a tidy page—
The Rabbit’s touch, a doc upgrade!
🐇✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.

---

Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Commit Unit Tests in branch feature/issue/350
• 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: 0

🧹 Nitpick comments (1)

docs/finishing-touches/docstrings.md (1)

63-79: Supported languages list is concise and well-ordered
Removing the previously unchecked entries—Haskell and Scala—makes the list unambiguous and it appears correctly sorted. Nit: consider changing “Php” to the canonical uppercase “PHP” to match common styling conventions.

🧰 Tools

🪛 LanguageTool

[duplication] ~64-~64: Possible typo: you repeated a word.
Context: ...hese languages are supported: - Bash - C - C# - C++ - Elixir - Go - Java - JavaScrip...

(ENGLISH_WORD_REPEAT_RULE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b0fdbf0 and e81c475.

📒 Files selected for processing (1)

• docs/finishing-touches/docstrings.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/finishing-touches/docstrings.md

[duplication] ~64-~64: Possible typo: you repeated a word.
Context: ...hese languages are supported: - Bash - C - C# - C++ - Elixir - Go - Java - JavaScrip...

(ENGLISH_WORD_REPEAT_RULE)

🔇 Additional comments (1)

docs/finishing-touches/docstrings.md (1)

53-55: Bulleted list for supported forges is clear and accurate
The conversion from checkboxes to simple bullets removes ambiguity, and the list now only reflects actively supported platforms (Azure DevOps, GitHub, GitLab). Great work.