docs: synchronizing help from snyk/user-docs

Author: Avishagp

help/cli-commands/code-test.md

@@ -29,7 +29,7 @@ You can use environment variables to configure the Snyk CLI and set variables fo
 
 Use the `-d` option to output the debug logs.
 
-## Options for the code test subcommand
+## Options
 
 ### `--org=<ORG_ID>`
 
@@ -47,6 +47,20 @@ Note that you can also use `--org=<orgslugname>`. The `ORG_ID` works in both the
 
 For more information see the article [How to select the organization to use in the CLI](https://docs.snyk.io/snyk-cli/test-for-vulnerabilities/how-to-select-the-organization-to-use-in-the-cli)
 
+### `--report`
+
+**NEW** option: Share results with the Snyk Web UI.
+
+**Feature availability**: This feature is currently in Closed Beta. To obtain access, contact your Snyk account representative.
+
+This creates a project in your Snyk account with a snapshot of the current configuration issues or appends the snapshot to an existing project.
+
+After using this option, log in to the Snyk website and view your projects to see the snapshot.
+
+Example: `$ snyk code test --report` --project-name="PROJECT_NAME"
+
+For more information see [Publishing CLI results to a Snyk Project](https://docs.snyk.io/scan-application-code/snyk-code/cli-for-snyk-code/publishing-cli-results-to-a-snyk-project-and-ignoring-cli-results#publishing-cli-results-to-a-snyk-project)
+
 ### `--json`
 
 Print results on the console as a JSON data structure.

help/cli-commands/container-monitor.md

@@ -124,7 +124,7 @@ For more information see [Detecting application vulnerabilities in container ima
 
 ### `--nested-jars-depth`
 
-When `app-vulns` is enabled, use the `--nested-jars-depth` option to set how many levels of nested jars Snyk is to unpack. Depth must be a number.
+When `app-vulns` is enabled, use the `--nested-jars-depth=n` option to set how many levels of nested jars Snyk is to unpack. Depth must be a number.
 
 ### `--exclude-base-image-vulns`
 

help/cli-commands/container-test.md

@@ -116,11 +116,11 @@ Allow disabling scans for app vulnerabilities; in CLI versions 1.1090.0 (2023-01
 
 In earlier releases, cannot be used with `--app-vulns`.
 
-For more information see [Detecting application vulnerabilities in container images](https://docs.snyk.io/products/snyk-container/getting-around-the-snyk-container-ui/detecting-application-vulnerabilities-in-container-images)
+For more information, see [Detecting application vulnerabilities in container images](https://docs.snyk.io/products/snyk-container/getting-around-the-snyk-container-ui/detecting-application-vulnerabilities-in-container-images)
 
 ### `--nested-jars-depth`
 
-When `app-vulns` is enabled, use the `--nested-jars-depth` option to set how many levels of nested jars Snyk is to unpack. Depth must be a number.
+When `app-vulns` is enabled, use the `--nested-jars-depth=n` option to set how many levels of nested jars Snyk is to unpack. Depth must be a number.
 
 ### `--exclude-base-image-vulns`
 
@@ -156,4 +156,8 @@ Specify a password to use when connecting to a container registry. This is ignor
 
 `$ snyk container test app:latest --file=Dockerfile --policy-path=path/to/.snyk`
 
-For more information and examples see [Advanced Snyk Container CLI usage](https://docs.snyk.io/snyk-container/snyk-cli-for-container-security/advanced-snyk-container-cli-usage)
+### Refer to a container image by its digest
+
+`$ snyk container test app@sha256:17cb37098f0efb819c075eea4ff2a495be909a396e86ece317a6e3a8968e025c --file=Dockerfile`
+
+For more information and examples, see [Advanced Snyk Container CLI usage](https://docs.snyk.io/snyk-container/snyk-cli-for-container-security/advanced-snyk-container-cli-usage)

help/cli-commands/iac-test.md

@@ -149,7 +149,9 @@ Set or override the remote URL for the repository.
 
 **NEW** option: Share results with the Snyk Web UI.
 
-This creates a project in your Snyk account with a snapshot of the current configuration issues. After using this option, log in to the Snyk website and view your projects to see the monitor.
+This creates a project in your Snyk account with a snapshot of the current configuration issues or appends the snapshot to an existing project.
+
+After using this option, log in to the Snyk website and view your projects to see the snapshot.
 
 Example: `$ snyk iac test --report`
 

help/cli-commands/ignore.md

@@ -72,6 +72,8 @@ Human-readable `<REASON>` to ignore this issue.
 
 Default: none
 
+**Note**: Not supported for Snyk Code.
+
 ### `--policy-path=<PATH_TO_POLICY_FILE>`
 
 Path to a `.snyk` policy file to pass manually.

help/cli-commands/sbom.md

@@ -87,18 +87,8 @@ Optional. Instruct the CLI to autodetect a package manager manifest file to use
 
 ### Create an SPDX 2.3 JSON document for an unmanaged software project
 
-```bash
-$ snyk sbom --unmanaged --format=spdx2.3+json
-```
+`$ snyk sbom --unmanaged --format=spdx2.3+json`
 
 ### Create a CycloneDX XML document for a Maven project
 
-```
-$ snyk sbom --file=pom.xml --format=cyclonedx1.4+xml
-```
-
-### **Create a CycloneDX JSON document and scan using bomber and Snyk**
-
-<pre class="language-bash"><code class="lang-bash"><strong>$ snyk sbom --format=cyclonedx1.4+json --file=go.mod > /tmp/sbom.cdx.json &#x26;&#x26; \
-</strong><strong>  bomber scan --provider snyk --token $SNYK_API_TOKEN /tmp/sbom.cdx.json
-</strong></code></pre>
+`$ snyk sbom --file=pom.xml --format=cyclonedx1.4+xml`