Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update test.md - stderr not stdout #1484

Merged
merged 2 commits into from
Nov 26, 2024
Merged

Update test.md - stderr not stdout #1484

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8d0bd5f
Update test.md - stderr not stdout
ryanlink Nov 26, 2024
8319afa
Update sbom.md - stderr not stdout
ryanlink Nov 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/references/subcommands/sbom.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ In addition to the [usual FOSSA project flags](#common-fossa-project-flags) supp

The `sbom test` command checks whether the most-recent scan of your FOSSA project raised license-policy or vulnerability issues. This command is usually run immediately after `fossa sbom analyze`.

- If there are issues, it prints them to stdout and fails with an exit code of 1
- If there are issues, it prints them to stderr and fails with an exit code of 1
- If there are no issues, it prints nothing and succeeds with an exit code of 0

`fossa sbom test` supports the [Common FOSSA Project Flags](./analyze.md#common-fossa-project-flags).
Expand Down
4 changes: 2 additions & 2 deletions docs/references/subcommands/test.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@

The test command checks whether the most-recent scan of your FOSSA project raised license-policy or vulnerability issues. This command is usually run immediately after `fossa analyze`

- If there are issues, it prints them to stdout and fails with an exit code of 1
- If there are issues, it prints them to stderr and fails with an exit code of 1
- If there are no issues, it prints nothing and succeeds with an exit code of 0

`fossa test` supports the [Common FOSSA Project Flags](./analyze.md#common-fossa-project-flags) supported by all commands
Expand Down Expand Up @@ -54,4 +54,4 @@ For instance,


* If the revision `v2.0.0` has issue: `A`, and the revision `34021e` has issues `A`, `B`,
* `fossa-cli` reports issue `B` and exits with status code of 1.
* `fossa-cli` reports issue `B` and exits with status code of 1.
Loading