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: README.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -917,6 +917,24 @@ git push --no-verify
917
917
> [!TIP]
918
918
> The pre-push hook is triggered on `git push` command and scans only the commits that are about to be pushed, making it more efficient than scanning the entire repository.
919
919
920
+
## Exclude Paths From Scans
921
+
You can use a `.cycodeignore` file to tell the Cycode CLI which files and directories to exclude from scans.
922
+
It works just like a `.gitignore` file. This helps you focus scans on your relevant code and prevent certain paths from triggering violations locally.
923
+
924
+
### How It Works
925
+
1. Create a file named `.cycodeignore` in your workfolder.
926
+
2. List the files and directories you want to exclude, using the same patterns as `.gitignore`.
927
+
3. Place this file in the directory where you plan to run the cycode scan command.
928
+
929
+
> [!WARNING]
930
+
> - **Invalid files**: If the `.cycodeignore` file contains a syntax error, the CLI scan will fail and return an error.
931
+
> - **Ignoring paths vs. violations**: This file is for excluding paths. It's different from the CLI's capability to ignore specific violations (for example, by using the --ignore-violation flag).
932
+
933
+
### Supported Scanners
934
+
- SAST
935
+
- Iac (comming soon)
936
+
- SCA (comming soon)
937
+
920
938
## Scan Results
921
939
922
940
Each scan will complete with a message stating if any issues were found or not.
0 commit comments