feat: Input Service Distribution (ISD) - #71
Conversation
Not up to standards ⛔🔴 Issues
|
| Category | Results |
|---|---|
| BestPractice | 1 minor |
| CodeStyle | 30 minor |
🟢 Metrics 0 complexity · 0 duplication
Metric Results Complexity 0 Duplication 0
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
Confidence Score: 5/5Documentation-only change with no logic; all asset references resolve correctly and the sidebar link is properly configured. All asset paths are in the right directories and match their references, the sidebar entry points to the correct route, and the new page is well-structured. The only finding is a missing trailing newline on the last line of miscellaneous_reports.md. No files require special attention.
|
| Filename | Overview |
|---|---|
| pages/.vitepress/config.mjs | Adds "Input Service Distribution" sidebar entry between Purchase Transaction and TDS Configuration — correct placement and link. |
| pages/docs/configuration/input_service_distribution.md | New ISD documentation page covering prerequisites, two creation flows (from Purchase Invoice and direct), external company setup, and credit notes — all four GIF asset references resolve correctly to the configuration/assets folder. |
| pages/docs/gst-reports/miscellaneous_reports.md | Adds ISD Invoice Register section with correct asset reference; missing trailing newline on the last line. |
Reviews (2): Last reviewed commit: "fix: added report's image" | Re-trigger Greptile
|
Warning Review limit reached
Next review available in: 35 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdded an Input Service Distribution documentation page covering concepts, prerequisites, invoice creation workflows, external-company handling, and credit-note reversals. Added an ISD Invoice Register subsection describing report views and related GST reporting. Updated the configuration sidebar to link to the new page. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
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. Comment |
PR: resilient-tech/india-compliance#4524