dependabot exclude paths

Not specified by the original author.

TL;DR

Use the exclude-paths option in the dependabot.yml update entry to list directories Dependabot should skip, e.g. the experiments folder. This applies per update entry, so set it on each ecosystem block that scans near the excluded paths.

Steps

1. Use the exclude-paths option in the dependabot.yml update entry to list directories Dependabot should skip, e.g. the experiments folder. This applies per update entry, so set it on each ecosystem block that scans near the excluded paths. It keeps the noise PRs away without moving the experiments out of the repo or disabling Dependabot for the directories you do care about.

When to use

You are seeing this: It keeps the noise PRs away without moving the experiments out of the repo or disabling Dependabot for the directories you do care about. Use this skill when you run into "Exclude directories like experiments from Dependabot updates".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #65275433 (accepted answer, 37 votes): the asker has an /experiments directory full of one-off package.json files they never intend to maintain, but Dependabot keeps opening PRs for them. The accepted answer notes this was impossible for years and is now supported via configuration.

Verified resolution: Use the exclude-paths option in the dependabot.yml update entry to list directories Dependabot should skip, e.g. the experiments folder. This applies per update entry, so set it on each ecosystem block that scans near the excluded paths. It keeps the noise PRs away without moving the experiments out of the repo or disabling Dependabot for the directories you do care about.

Source URL: https://stackoverflow.com/questions/65275433/can-i-exclude-directories-from-github-dependabot

Not specified by the original author.

TL;DR

To exclude directories for the open source part, you need to: In an SCM import, add the list to exclude (screenshot) In a CLI import, add the directories as arguments (syntax below) --exclude=DIRECTORY[,DIRECTORY]...> (only in test and monitor commands) Can be used with --all-projects and --yarn-workspaces to indicate sub-directories and files to exclude. This is confusing because these are two separate mechanisms.

When to use

You are seeing this: From the accepted Stack Overflow answer: Yes, unfortunately this is confusing today. Use this skill when you run into "How do we ignore folders in Snyk".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

From the accepted Stack Overflow answer: Yes, unfortunately this is confusing today. For historical reasons, the .snyk file only applies to Snyk Code (SAST). To exclude directories for the open source part, you need to: In an SCM import, add the list to exclude (screenshot) In a CLI import, add the directories as arguments (syntax below) --exclude=DIRECTORY[,DIRECTORY]...> (only in test and monitor commands) Can be used with --all-projects and --yarn-workspaces to indicate sub-directories and files to exclude. Must be comma separated. This is confusing because these are two separate mechanisms. In the future, both mechanisms will be the same, but for now, both need to be done.

Context: Problem: Accepted solution (score 5): Yes, unfortunately this is confusing today. For historical reasons, the .snyk file only applies to Snyk Code (SAST). To exclude directories for the open source part, you need to: In an SCM import, add the list to exclude (screenshot) In a CLI import, add the directories as arguments (syntax below) --exclude=DIRECTORY[,DIRECTORY]...> (only in test and monitor commands) Can be used with --all-projects and --yarn-workspaces to indicate sub-directories and files to exclude. Must be comma separated. This is confusing because these are two separate mechanisms. In the future, both mechanisms will be the same, but for now, both need to be done.

Source: Problem: Accepted solution (score 5): Yes, unfortunately this is confusing today. For historical reasons, the .snyk file only applies to Snyk Code (SAST). To exclude directories for the open source part, you need to: In an SCM import, add the list to exclude (screenshot) In a CLI import, add the directories as arguments (syntax below) --exclude=DIRECTORY[,DIRECTORY]...> (only in test and monitor commands) Can be used with --all-projects and --yarn-workspaces to indicate sub-directories and files to exclude. Must be comma separated. This is confusing because these are two separate mechanisms. In the future, both mechanisms will be the same, but for now, both need to be done.

Verified resolution: From the accepted Stack Overflow answer: Yes, unfortunately this is confusing today. For historical reasons, the .snyk file only applies to Snyk Code (SAST). To exclude directories for the open source part, you need to: In an SCM import, add the list to exclude (screenshot) In a CLI import, add the directories as arguments (syntax below) --exclude=DIRECTORY[,DIRECTORY]...> (only in test and monitor commands) Can be used with --all-projects and --yarn-workspaces to indicate sub-directories and files to exclude. Must be comma separated. This is confusing because these are two separate mechanisms. In the future, both mechanisms will be the same, but for now, both need to be done.

Source URL: https://stackoverflow.com/questions/76145644/how-do-we-ignore-folders-in-snyk

Not specified by the original author.

TL;DR

Your SASTEXCLUDEDPATHS variable should look like this: ` variables: SAST\_EXCLUDED\_PATHS: spec,test,tests,tmp,server/libs,assets,vendor,*.min.js Context: Stack Overflow #70887133 (accepted answer, 10 votes, 2 answers): I have enabled SAST scanning in GitLab CI (GitLab Community Edition) 14.5.2.

Steps

1. [Sencha23 (accepted answer)] Hope I'm not too late. I've encountered the same problem and what resolved it for me was to delete the space between the excluded paths. Your SASTEXCLUDEDPATHS variable should look like this:

## When to use

You are seeing this: [Sencha23 (accepted answer)] Hope I'm not too late. Use this skill when you run into "Why is GitLab CI SAST not exluding directories that I ask it to exclude?".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: Edition 14.5.2. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #70887133 (accepted answer, 10 votes, 2 answers): I have enabled SAST scanning in GitLab CI (GitLab Community Edition) 14.5.2. The SAST runs tools like semgrep and ESLint run over the source code and scan for vulnerabilities. This works... except it's not excluding paths and files from the results that I tell it to so my reports are filled with junk from 3rd party libs. Since I don't want test code or 3rd party stuff in the report I use the GitLab provided variable for this purpose called SASTEXCLUDEDPATHS that I use to exclude some dirs. My value is like this: ``` variables: SASTEXCLUDEDPATHS: spec, test, tests, tmp, server

Verified resolution: [Sencha23 (accepted answer)] Hope I'm not too late. I've encountered the same problem and what resolved it for me was to delete the space between the excluded paths. Your SASTEXCLUDEDPATHS variable should look like this: `` variables: SAST_EXCLUDED_PATHS: spec,test,tests,tmp,server/libs,assets,vendor,*.min.js

Source URL: https://stackoverflow.com/questions/70887133