Can i choose which files to exclude from scanning in the git-secrets-scan pipe?

[Abdelmassih Abdelmassih]

I can not find any documentation regarding files/folders exclusion from git-secrets-scan pipe in bitbuckets pipelines

[Igor Stoyanov]

Hi @Abdelmassih Abdelmassih. Please, check the docs.
You should add paths under [allowlist] section in gitleaks.toml file.
Example:

# This is a global allowlist which has a higher order of precedence than rule-specific allowlists.
# If a commit listed in the `commits` field below is encountered then that commit will be skipped and no
# secrets will be detected for said commit. The same logic applies for regexes and paths.
[allowlist]
description = "global allow list"
commits = [ "commit-A", "commit-B", "commit-C"]
paths = [
  '''gitleaks\.toml''',
  '''(.*?)(jpg|gif|doc)'''
]

Regards, Igor

[Sahir Maharaj]

Hello @Abdelmassih Abdelmassih

Based on my experience, the git-secrets-scan pipe in Bitbucket Pipelines currently doesn’t seem to have explicit documentation or built-in options for excluding specific files or folders.

However, you can achieve this indirectly by modifying your pipeline configuration to exclude certain paths from being scanned. This could involve creating a .gitignore-like file or customizing the script that invokes the pipe to filter files.

Opening a ticket with Atlassian support at https://support.atlassian.com/contact/#/ may provide clarity or a workaround.