-
-
Notifications
You must be signed in to change notification settings - Fork 849
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
fix: update code to support @octokit/request v9 and @octokit/graphql v8 #3697
base: master
Are you sure you want to change the base?
Conversation
Warning Rate limit exceeded@AritraDey-Dev has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 20 minutes and 7 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (2)
WalkthroughThe pull request updates the Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 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
Documentation and Community
|
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.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
@AritraDey-Dev Make sure all the tests and build pass |
1320dd5
to
2cad54c
Compare
This reverts commit 2cad54c.
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.
Actionable comments posted: 0
🔭 Outside diff range comments (1)
scripts/dashboard/build-dashboard.js (1)
180-180
:⚠️ Potential issueUpdate the module execution check for ES modules
The
require.main === module
check is specific to CommonJS and won't work in an ES module environment. This line needs to be updated to the ES module equivalent.- if (require.main === module) { + if (import.meta.url === `file://${process.argv[1]}`) {
🧹 Nitpick comments (1)
scripts/dashboard/build-dashboard.js (1)
184-184
: Successfully migrated to ES module exportsThe export statement has been correctly migrated from CommonJS
module.exports
to ES moduleexport
.For better readability, consider formatting the exports with each name on a separate line as suggested by the linter:
- export { getLabel, monthsSince, mapGoodFirstIssues, getHotDiscussions, getDiscussionByID, getDiscussions, writeToFile, start, processHotDiscussions, pause }; + export { + getLabel, + monthsSince, + mapGoodFirstIssues, + getHotDiscussions, + getDiscussionByID, + getDiscussions, + writeToFile, + start, + processHotDiscussions, + pause + };🧰 Tools
🪛 ESLint
[error] 184-184: Replace
·getLabel,·monthsSince,·mapGoodFirstIssues,·getHotDiscussions,·getDiscussionByID,·getDiscussions,·writeToFile,·start,·processHotDiscussions,·pause·
with⏎··getLabel,⏎··monthsSince,⏎··mapGoodFirstIssues,⏎··getHotDiscussions,⏎··getDiscussionByID,⏎··getDiscussions,⏎··writeToFile,⏎··start,⏎··processHotDiscussions,⏎··pause⏎
(prettier/prettier)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
scripts/dashboard/build-dashboard.js
(2 hunks)
🧰 Additional context used
🪛 ESLint
scripts/dashboard/build-dashboard.js
[error] 4-4: Unexpected use of file extension "js" for "./issue-queries.js"
(import/extensions)
[error] 184-184: Replace ·getLabel,·monthsSince,·mapGoodFirstIssues,·getHotDiscussions,·getDiscussionByID,·getDiscussions,·writeToFile,·start,·processHotDiscussions,·pause·
with ⏎··getLabel,⏎··monthsSince,⏎··mapGoodFirstIssues,⏎··getHotDiscussions,⏎··getDiscussionByID,⏎··getDiscussions,⏎··writeToFile,⏎··start,⏎··processHotDiscussions,⏎··pause⏎
(prettier/prettier)
🔇 Additional comments (1)
scripts/dashboard/build-dashboard.js (1)
1-4
: Successfully migrated to ES module importsThe imports have been properly migrated from CommonJS
require
statements to ES moduleimport
statements, which aligns with the PR objective to update Octokit dependencies.Note: The ESLint warning about file extensions is a configuration issue. Including
.js
extensions in imports is actually required for ES modules in Node.js environments.🧰 Tools
🪛 ESLint
[error] 4-4: Unexpected use of file extension "js" for "./issue-queries.js"
(import/extensions)
fixes #3690
Description
Update
package.json
to support@octokit/request
v9.2.2 and@octokit/graphql
v8.2.1.@octokit/graphql
to version8.2.1
.@octokit/request
with version9.2.2
.Summary by CodeRabbit
>=16
and npm version^8.0.0
.