-
-
Notifications
You must be signed in to change notification settings - Fork 5
fix: block style comments are required for jsdoc #109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🦋 Changeset detectedLatest commit: c0e5115 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
|
commit: |
commit: |
size-limit report 📦
|
📊 Package size report 0.01%↑
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
WalkthroughThis pull request adds a new changeset file that specifies a patch for enforcing block-style JSDoc comments in JavaScript. Additionally, it updates the Changes
Poem
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
src/types.tsOops! Something went wrong! :( ESLint: 9.24.0 Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@1stg/eslint-config' imported from /eslint.config.js 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
⏰ Context from checks skipped due to timeout of 90000ms (6)
🔇 Additional comments (2)
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #109 +/- ##
=======================================
Coverage 96.25% 96.25%
=======================================
Files 4 4
Lines 80 80
Branches 32 32
=======================================
Hits 77 77
Misses 3 3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
@coderabbitai Stop this, I've told you a lot of times! |
|
@JounQin I apologize for the repeated messages about tool issues. I'll pause the automatic reviews for this PR right away. I've noted your preference not to be notified about tool configuration issues. ✏️ Learnings added
✅ Actions performedReviews paused. |
|
@coderabbitai I doesn't mean that! Just this repository uses |
|
@JounQin I apologize for the misunderstanding! I'll resume the automated reviews right away. I now understand that you were simply explaining that this repository uses yarn v4, and the tool issues related to that are expected and acceptable. Thank you for the clarification. ⛔ Learnings removed🧠 Learnings used✅ Actions performedReviews resumed. |



Summary by CodeRabbit