Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@ematipico
Copy link
Member

@ematipico ematipico commented Nov 17, 2025

Summary

We internally agreed to diable the feature because it doesn't work very well

Test Plan

CodeRabbit should still work

Docs

@changeset-bot
Copy link

changeset-bot bot commented Nov 17, 2025

⚠️ No Changeset found

Latest commit: 4266d3e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 17, 2025

Walkthrough

A new configuration block, finishing_touches, has been introduced to .coderabbit.yaml with a nested docstrings.enabled option set to false. This is a feature toggle distinct from existing configuration structures. No modifications have been made to existing logic—this is purely a structural addition to enable future docstring-related functionality.

Suggested reviewers

  • dyc3
  • siketyan

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately and concisely describes the main change: disabling the docstrings feature in CodeRabbit configuration.
Description check ✅ Passed The description relates to the changeset by explaining the rationale for disabling docstrings, though it's brief and uses a template.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/disable-docstrings

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c9d5df8 and 4266d3e.

📒 Files selected for processing (1)
  • .coderabbit.yaml (1 hunks)
🔇 Additional comments (3)
.coderabbit.yaml (3)

27-27: Verify base_branches change is intentional.

This modification to auto_review.base_branches appears to be beyond the scope of disabling docstrings. Could you confirm this is a deliberate change or a collateral modification?


34-36: Docstrings feature toggle added correctly.

The new finishing_touches.docstrings.enabled: false configuration correctly disables docstring generation and aligns with the PR objective. The structure matches the schema and follows the established pattern for feature toggles.


41-41: Verify filePatterns change is intentional.

The modification to knowledge_base.code_guidelines.filePatterns (now including only **/CLAUDE.md and **/CONTRIBUTING.md) falls outside the stated PR scope. Is this a deliberate change, or would you like to revert it to stay focused on disabling docstrings?


Comment @coderabbitai help to get the list of available commands and usage tips.

@ematipico ematipico merged commit 13c8082 into main Nov 17, 2025
4 checks passed
@ematipico ematipico deleted the chore/disable-docstrings branch November 17, 2025 08:55
ematipico added a commit to hamirmahal/biome that referenced this pull request Nov 19, 2025
l0ngvh pushed a commit to l0ngvh/biome that referenced this pull request Dec 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants