Add rendergraph to releases
#1558
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Cortez and I are working with a customer that would benefit from having our internal
rendergraphtool being public; this PR adds it to the FOSSA CLI repository and releases.rendergraphitself is sort of a "best effort" tool so it doesn't have tests; I don't think it's worth adding to docs as we would expect users to basically use this when we suggest it for troubleshooting.Acceptance criteria
rendergraphis available in FOSSA CLI releases.Testing plan
Sadly, just manual testing
Risks
Yet more random stuff plugged into FOSSA CLI releases 🙃
Metrics
None
References
None
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.