Fast, portable and reliable dependency analysis for any codebase. Supports license & vulnerability scanning for large monoliths. Language-agnostic; integrates with 20+ build systems.
There was some ambiguity with some of our messaging around waiting for build completion. This PR:
Changes the message from "Waiting for build completion" to "Checking for build completion" unless the CLI gets back a status indicating it needs to wait.
Includes the revision that it's checking/waiting for in the message.
I also specified in license scanning results upload that it's a license result we're uploading. I was viewing some debug logs and it wasn't immediately clear to me that license results were what was getting uploaded.
[ ] I added tests for this PR's change (or explained in the PR description why tests don't make sense).
[ ] If this PR introduced a user-visible change, I added documentation into docs/.
[ ] If this PR added docs, I added links as appropriate to the user manual's ToC in docs/README.ms and gave consideration to how discoverable or not my documentation is.
[ ] If this change is externally visible, I updated Changelog.md. If this PR did not mark a release, I added my changes into an # Unreleased section at the top.
[ ] If I made changes to .fossa.yml or fossa-deps.{json.yml}, I updated docs/references/files/*.schema.json AND I have updated example files used by fossa init command. You may also need to update these if you have added/removed new dependency type (e.g. pip) or analysis target type (e.g. poetry).
[ ] If I made changes to a subcommand's options, I updated docs/references/subcommands/<subcommand>.md.
Overview
There was some ambiguity with some of our messaging around waiting for build completion. This PR:
I also specified in license scanning results upload that it's a license result we're uploading. I was viewing some debug logs and it wasn't immediately clear to me that license results were what was getting uploaded.
References
Slack
Checklist
docs/.docs/README.msand gave consideration to how discoverable or not my documentation is.Changelog.md. If this PR did not mark a release, I added my changes into an# Unreleasedsection at the top..fossa.ymlorfossa-deps.{json.yml}, I updateddocs/references/files/*.schema.jsonAND I have updated example files used byfossa initcommand. You may also need to update these if you have added/removed new dependency type (e.g.pip) or analysis target type (e.g.poetry).docs/references/subcommands/<subcommand>.md.