docs: add local testing steps to NestBot development guide#4352
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Summary by CodeRabbit
WalkthroughReformatted the "Testing NestBot Locally" guidance in CONTRIBUTING.md to present smoke-test steps as three explicit bullets: direct message, channel mention, and channel message when subscribed to the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
No issues found across 1 file
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Since this is your first cubic review, here's how it works:
- cubic automatically reviews your code and comments on bugs and improvements
- Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
- Add one-off context when rerunning by tagging
@cubic-dev-aiwith guidance or docs links (includingllms.txt) - Ask questions if you need clarification on any suggestion
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@CONTRIBUTING.md`:
- Around line 268-283: Update the markdown under the "Testing NestBot Locally"
subsection: change the h6 heading to the next-level heading (increment by one
from the parent h4) so heading levels are sequential, and ensure the fenced code
block around the make run snippet has a blank line before and after it to
satisfy markdownlint; locate the "Testing NestBot Locally" heading and the
fenced block containing "make run" to apply these adjustments.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: f8245311-c403-457c-a438-4ec68f9f624b
📒 Files selected for processing (1)
CONTRIBUTING.md
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@CONTRIBUTING.md`:
- Line 278: Remove the trailing whitespace on the blank line in CONTRIBUTING.md
that triggers markdownlint MD009; open the file, find the empty/blank line
containing extra spaces, trim those spaces so the line is truly empty, save and
re-run linting to ensure the MD009 warning is cleared.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 333712b5-f037-4d32-9c7d-a31f7fd51e88
📒 Files selected for processing (1)
CONTRIBUTING.md
There was a problem hiding this comment.
♻️ Duplicate comments (1)
CONTRIBUTING.md (1)
277-278:⚠️ Potential issue | 🟡 MinorAdd a blank line after the fenced block to satisfy markdownlint.
At Line 277, the closing fence is immediately followed by a list item on Line 278; MD031 expects a blank line there.
Suggested patch
```bash make run ``` + 1. **Direct Message**: Send a direct message to the bot in your Slack workspace.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@CONTRIBUTING.md` around lines 277 - 278, The closing fenced code block is immediately followed by a list item which violates MD031; add a single blank line after the closing triple backticks so the fence is separated from the following list entry. Locate the closing fence for the code block shown in the diff and insert one empty line before the "1. **Direct Message**: Send a direct message to the bot in your Slack workspace." list item to satisfy markdownlint.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@CONTRIBUTING.md`:
- Around line 277-278: The closing fenced code block is immediately followed by
a list item which violates MD031; add a single blank line after the closing
triple backticks so the fence is separated from the following list entry. Locate
the closing fence for the code block shown in the diff and insert one empty line
before the "1. **Direct Message**: Send a direct message to the bot in your
Slack workspace." list item to satisfy markdownlint.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 189b763d-db53-4fd5-b14a-d84cbd73983f
📒 Files selected for processing (1)
CONTRIBUTING.md
arkid15r
dismissed stale reviews from coderabbitai[bot] and cubic-dev-ai[bot]
via
806bf33
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4352 +/- ##
=======================================
Coverage 99.05% 99.05%
=======================================
Files 527 527
Lines 16882 16882
Branches 2320 2320
=======================================
Hits 16723 16723
Misses 91 91
Partials 68 68
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
2 participants
Resolves #4333
Added a "Testing NestBot Locally" section to help contributors verify their setup.
Includes: