Skip to content

chore: add standard CodeRabbit configuration file#304

Open
Muneerali199 wants to merge 2 commits intoAOSSIE-Org:devfrom
Muneerali199:add-coderabbit-config-upstream
Open

chore: add standard CodeRabbit configuration file#304
Muneerali199 wants to merge 2 commits intoAOSSIE-Org:devfrom
Muneerali199:add-coderabbit-config-upstream

Conversation

@Muneerali199
Copy link
Copy Markdown
Contributor

@Muneerali199 Muneerali199 commented Feb 21, 2026

Description

Adds the standard .coderabbit.yaml from the AOSSIE Template-Repo to align CodeRabbit settings across org repos. This is a low-risk config-only change. Addressing CodeRabbit's feedback to make the config web-appropriate for this Next.js project.

Fixes # (no specific issue - adding standard org config)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (does not change functionality, e.g. code style improvements, linting)
  • Documentation update
  • New release (version bump, release preparation)
  • UI/UX update (design changes, interface improvements)
  • CI/CD & Tooling (workflow, build, or dev tool changes)
  • Dependency update (package upgrades or deprecation fixes)

How Has This Been Tested?

This is a configuration-only change with no runtime code changes.

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
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings

Maintainer Checklist

  • Tag the PR with the appropriate labels

Summary by CodeRabbit

  • Chores
    • Updated CodeRabbit configuration to be web-appropriate for this Next.js project:
      • Fixed schema error by moving general instructions to path_instructions
      • Updated 'use client' guidance to recommend conditional usage
      • Replaced mobile-specific rules with web-appropriate security and testing guidance
      • Updated asset review to use responsive image patterns instead of @2x/@3x

Summary by CodeRabbit

  • Chores
    • Added automated code review configuration to improve development workflow with automated review processes, issue labeling, and code quality tooling integration.

@Muneerali199 Muneerali199 requested a review from a team as a code owner February 21, 2026 08:17
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Feb 21, 2026

📝 Walkthrough

Walkthrough

A single new .coderabbit.yaml file adds a comprehensive CodeRabbit configuration enabling IDE schema autocompletion, automated review workflows, multi-tool linting/security checks, label-driven planning/enrichment, PR lifecycle controls, path filters, and detailed, language-scoped review instructions.

Changes

Cohort / File(s) Summary
Configuration File
./.coderabbit.yaml
Adds a new CodeRabbit configuration defining IDE schema-backed autocompletion, review language/early_access/chat settings, issue enrichment and label rules, planning rules, auto-review and request-changes workflows, pre-merge checks, path exclude filters, broad tooling integrations (linters/security/static analysis), PR labeling by language/domain, and extensive path-scoped review instructions for TypeScript/JS, Python, Solidity, HTML/CSS, tests, and assets.

Sequence Diagram(s)

sequenceDiagram
    rect rgba(200,220,255,0.5)
    participant Dev as Developer (PR)
    end
    rect rgba(220,255,200,0.5)
    participant GH as GitHub (PR)
    end
    rect rgba(255,240,200,0.5)
    participant CR as CodeRabbit (config)
    end
    rect rgba(255,200,200,0.5)
    participant Tools as Linters / Scanners
    end

    Dev->>GH: Open PR (title, branch, files)
    GH->>CR: Deliver PR metadata & files
    CR->>Tools: Trigger configured linters/security checks
    Tools-->>CR: Return tool reports
    CR->>CR: Apply path filters, labeling, planning rules
    CR->>GH: Post automated review (summary, labels, diagrams, poem, status)
    GH->>Dev: Notify (review comments, labels, required checks)
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Suggested labels

enhancement

Poem

🐰 In burrows of YAML I quietly dwell,

Rules and linters tuned like a bell,
Labels planted, checks set to run,
Reviews automated — a job well done,
Hoppity-hop, the repo's now well!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: adding a standard CodeRabbit configuration file (.coderabbit.yaml). It is concise, clear, and directly reflects the changeset's primary purpose.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

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

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

🧹 Nitpick comments (1)
.coderabbit.yaml (1)

273-280: Asset review instructions are mobile-centric for a website project.

@2x and @3x variants are an iOS/mobile convention. For web projects, consider referencing responsive images (srcset), WebP/AVIF formats, and appropriate compression instead.

Suggested update
     - path: "assets/**/*"
       instructions: |
         Review asset files for:
         - Image optimization (appropriate size and format)
-        - Proper `@2x` and `@3x` variants for different screen densities
+        - Responsive image variants or use of modern formats (WebP, AVIF)
         - SVG assets are optimized
         - Font files are licensed and optimized
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.coderabbit.yaml around lines 273 - 280, The asset review checklist under
the "assets/**/*" entry is mobile/iOS-centric (mentions `@2x` and `@3x`); update it
to web-appropriate guidance by replacing references to `@2x/`@3x with responsive
image practices such as using srcset and sizes, recommending modern formats
(WebP/AVIF), ensuring proper compression and responsive breakpoints, confirming
optimized SVGs, and verifying licensed/subsetted fonts—keep the checklist
focused on web delivery, performance, and responsive behavior.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.coderabbit.yaml:
- Around line 67-68: The inline comment for the configuration key
request_changes_workflow is misleading: it currently says "(just leave
comments)" but request_changes_workflow: true actually files a "Request Changes"
review that blocks the PR until comments are addressed then auto-approves;
update the comment next to request_changes_workflow to accurately describe this
behavior (or flip the boolean if the intended behavior was to only leave
comments) and keep the comment succinctly stating the exact effect (e.g., "when
true, submit a Request Changes review that blocks the PR until addressed, then
auto-approves").
- Around line 248-257: Update the test guidance entry that currently references
"@testing-library/react-native" to use "@testing-library/react" because this is
a web project; locate the YAML block matching the test path pattern
"**/*.test.{ts,tsx,js,jsx}" and replace the `@testing-library/react-native`
mention in the instructions with `@testing-library/react`, ensuring the rest of
the checklist (coverage, async, accessibility, descriptions, non-tautological
tests) remains unchanged.
- Around line 170-186: The instruction "Ensure that 'use client' is being used"
is too broad; change it to advise conditional use only when client-side features
are required. Replace that line with wording like: "Ensure 'use client' is added
only for components that require client-side behavior (React hooks, event
handlers, browser APIs, or stateful UI); prefer server components by default to
retain Next.js App Router performance benefits" and update the rule text in the
YAML (the string "Ensure that 'use client' is being used") accordingly so
linters/guidance will only flag true client-side needs.
- Around line 188-197: The YAML contains mobile-specific rules that don't apply
to this Next.js web project; remove references to expo-secure-store,
`@testing-library/react-native`, and `@2x/`@3x image conventions and replace them
with web-appropriate guidance: recommend httpOnly/secure/SameSite cookies or
localStorage+CSRF protections for tokens, suggest using the Web Crypto API for
sensitive operations, swap `@testing-library/react-native` for
`@testing-library/react`, and replace `@2x/`@3x image guidance with responsive image
patterns (srcset, sizes, modern formats). Update the security checklist entries
that mention "expo-secure-store", "@testing-library/react-native", and "@2x/@3x"
to these web-specific alternatives and remove any React Native-only tooling or
wording.
- Around line 152-166: The YAML contains an invalid top-level
reviews.instructions property; remove or move this block out of reviews and
instead add it under path_instructions as a catch-all entry. Specifically,
delete the reviews.instructions key and create a path_instructions item with
path: "**/*" and an instructions scalar containing the listed rules (use the
path_instructions and instructions keys so the schema accepts it). Ensure you do
not add additional top-level properties forbidden by the schema and keep the
exact instruction text under the new path_instructions.entry.

---

Nitpick comments:
In @.coderabbit.yaml:
- Around line 273-280: The asset review checklist under the "assets/**/*" entry
is mobile/iOS-centric (mentions `@2x` and `@3x`); update it to web-appropriate
guidance by replacing references to `@2x/`@3x with responsive image practices such
as using srcset and sizes, recommending modern formats (WebP/AVIF), ensuring
proper compression and responsive breakpoints, confirming optimized SVGs, and
verifying licensed/subsetted fonts—keep the checklist focused on web delivery,
performance, and responsive behavior.

Comment thread .coderabbit.yaml Outdated
Comment thread .coderabbit.yaml Outdated
Comment thread .coderabbit.yaml
Comment thread .coderabbit.yaml
Comment thread .coderabbit.yaml
@reach2saksham
Copy link
Copy Markdown

Hi @Muneerali199, can you use our org's PR template for this, linking the parent issue? Can you also please address CodeRabbitAI's suggestions

- Fix request_changes_workflow comment to accurately describe behavior
- Move general instructions to path_instructions to fix schema error
- Update 'use client' guidance to recommend conditional usage
- Replace expo-secure-store with web-appropriate storage guidance
- Replace @testing-library/react-native with @testing-library/react
- Replace @2x/@3x image guidance with responsive image patterns
@Muneerali199
Copy link
Copy Markdown
Contributor Author

review @coderabbitai

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 26, 2026

@Muneerali199 Sure, I'll start a new review of the PR now!

Note: The previous reviewer (@reach2saksham) has also asked you to:

  1. Use the organization's PR template and link the parent issue.
  2. Address any prior CodeRabbit suggestions before merging.

Please make sure those are addressed as part of this PR.

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@Muneerali199 Muneerali199 changed the base branch from main to dev March 26, 2026 08:54
@Muneerali199
Copy link
Copy Markdown
Contributor Author

Muneerali199 commented Mar 26, 2026

hey @reach2saksham ,please check it now. i done all changes you request

Copy link
Copy Markdown
Contributor

@aniket866 aniket866 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGMT

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