You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md
+60Lines changed: 60 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -686,6 +686,66 @@ When `target-branch` is defined:
686
686
* All pull requests for version updates are opened targeting the specified branch.
687
687
* Options defined for this `package-ecosystem` no longer apply to security updates because security updates always use the default branch for the repository.
Use to specify paths of directories and files that {% data variables.product.prodname_dependabot %} should ignore when scanning for manifests and dependencies. This option is useful when you want to prevent updates for dependencies in certain locations, such as test assets, vendored code, or specific files.
692
+
693
+
{% data variables.product.prodname_dependabot %} default behavior:
694
+
695
+
* All directories and files in the specified `directory` are included in the update scan unless excluded by this option.
696
+
697
+
When `exclude-paths` is defined:
698
+
699
+
* All files and directories matching the specified paths are ignored during update scans for the given `package-ecosystem` entry.
700
+
701
+
| Parameter | Purpose |
702
+
|-----------|---------|
703
+
| `exclude-paths` | A list of glob patterns for files or directories to ignore. |
704
+
705
+
Glob patterns are supported, such as `**` for recursive matching and `*` for single-segment wildcards. Patterns are relative to the `directory` specified for the update configuration. Each ecosystem can have its own `exclude-paths` settings.
706
+
707
+
## Example
708
+
709
+
```yaml copy
710
+
version: 2
711
+
updates:
712
+
- package-ecosystem: "npm"
713
+
directory: "/"
714
+
schedule:
715
+
interval: "daily"
716
+
exclude-paths:
717
+
- "src/test/assets"
718
+
- "vendor/**"
719
+
- "src/*.js"
720
+
- "src/test/helper.js"
721
+
722
+
# Sample patterns that can be used-
723
+
724
+
# Pattern: docs/*.json
725
+
# Matches: docs/foo.json, docs/bar.json
726
+
727
+
# Pattern: *.lock
728
+
# Matches: Gemfile.lock, package.lock, foo.lock (in any directory)
In this example, {% data variables.product.prodname_dependabot %} will ignore the `src/test/assets` directory, all files under `vendor/`, all JavaScript files directly under `src/`, and the specific file `src/test/helper.js` when scanning for updates.
Copy file name to clipboardExpand all lines: content/code-security/secret-scanning/introduction/supported-secret-scanning-patterns.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,21 +76,21 @@ In addition to these generic non-provider patterns, {% data variables.product.pr
76
76
> [!NOTE]
77
77
> Validity checks are only available to users with {% data variables.product.prodname_team %} or {% data variables.product.prodname_enterprise %} who enable the feature as part of {% data variables.product.prodname_GH_secret_protection %}.
0 commit comments