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
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -281,7 +281,7 @@ The following are the options and commands available with the Cycode CLI applica
281
281
| [auth](#using-the-auth-command) | Authenticate your machine to associate the CLI with your Cycode account. |
282
282
| [configure](#using-the-configure-command) | Initial command to configure your CLI client authentication. |
283
283
| [ignore](#ignoring-scan-results) | Ignores a specific value, path or rule ID. |
284
-
| [scan](#running-a-scan) | Scan the content for Secrets/IaC/SCA/SAST violations. You`ll need to specify which scan type to perform: commit_history/path/repository/etc. |
284
+
| [scan](#running-a-scan) | Scan the content for Secrets/IaC/SCA/SAST violations. You`ll need to specify which scan type to perform: commit-history/path/repository/etc. |
285
285
| [report](#report-command) | Generate report. You`ll need to specify which report type to perform. |
286
286
| status | Show the CLI status and exit. |
287
287
@@ -294,7 +294,7 @@ The Cycode CLI application offers several types of scans so that you can choose
| [commit_history](#commit-history-scan) | Scan all the commits history in this git repository |
311
+
| [commit-history](#commit-history-scan) | Scan all the commits history in this git repository |
312
312
| [path](#path-scan) | Scan the files in the path supplied in the command |
313
-
| [pre_commit](#pre-commit-scan) | Use this command to scan the content that was not committed yet |
313
+
| [pre-commit](#pre-commit-scan) | Use this command to scan the content that was not committed yet |
314
314
| [repository](#repository-scan) | Scan git repository including its history |
315
315
316
316
### Options
@@ -466,25 +466,25 @@ A commit history scan is limited to a local repository’s previous commits, foc
466
466
467
467
To execute a commit history scan, execute the following:
468
468
469
-
`cycode scan commit_history {{path}}`
469
+
`cycode scan commit-history {{path}}`
470
470
471
471
For example, consider a scenario in which you want to scan the commit history for a repository stored in `~/home/git/codebase`. You could then execute the following:
472
472
473
-
`cycode scan commit_history ~/home/git/codebase`
473
+
`cycode scan commit-history ~/home/git/codebase`
474
474
475
475
The following options are available for use with this command:
| `-r, --commit_range TEXT` | Scan a commit range in this git repository, by default cycode scans all commit history (example: HEAD~1) |
479
+
| `-r, --commit-range TEXT` | Scan a commit range in this git repository, by default cycode scans all commit history (example: HEAD~1) |
480
480
481
481
#### Commit Range Option
482
482
483
-
The commit history scan, by default, examines the repository’s entire commit history, all the way back to the initial commit. You can instead limit the scan to a specific commit range by adding the argument `--commit_range` (`-r`) followed by the name you specify.
483
+
The commit history scan, by default, examines the repository’s entire commit history, all the way back to the initial commit. You can instead limit the scan to a specific commit range by adding the argument `--commit-range` (`-r`) followed by the name you specify.
484
484
485
485
Consider the previous example. If you wanted to scan only specific commits in your repository, you could execute the following:
0 commit comments