Skip to content

ci: disable dependabot for npm #130

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.

Sign up for GitHub

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

Merged
9romise merged 1 commit into from
Jun 2, 2026
Merged

ci: disable dependabot for npm #130

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/dependabot.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,8 @@ updates:
directory: /
schedule:
interval: weekly
- package-ecosystem: npm
directory: /
schedule:
interval: weekly
open-pull-requests-limit: 0
Comment on lines +7 to +11
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Jun 2, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify npm package files exist in repository root

# Check for package.json and package-lock.json in root
fd -t f '^package\.json$|^package-lock\.json$' -d 1

# Also check if npm packages exist anywhere in the repo
fd -t f '^package\.json$' -d 3

Repository: npmx-dev/vscode-npmx

Length of output: 377

Clarify npm “disable” intent: open-pull-requests-limit: 0 stops PRs but not the weekly checks

  • The repo root has a package.json (but no package-lock.json in root), so the directory: / npm config will still run against root package.json; open-pull-requests-limit: 0 will suppress PR creation rather than disable Dependabot’s scheduled runs.
  • If the goal is full disablement, remove the npm updates entry; if the goal is “checks only / no PRs”, update the PR title/description to match that intent.

Loading