megamono feedback
Syntax, options, and usage for the feedback command.
Report an error or suggest an improvement from the command line. Include what you were trying to do, what happened, and what you expected.
Prepare a useful report
Generate a local report without signing in:
megamono feedback --jsonReview the report before sharing it in a GitHub issue. Include the command and Megamono version, and reduce the problem to a small example when possible. Leave out tokens, credentials, private source code, and customer data.
The public hosted service has not launched. The --submit option requires hosted authentication and is not available through the public service yet; local report generation works without it.
Command options
Use the help below for exact syntax and options. You can also run megamono feedback --help in your terminal.
Usage: megamono feedback [--json] [--packages=<names>]
[--yalc-store=<directory>] [--source-root=<repository>]
Create a redacted artifact report for manual review, sharing, or submission.
Includes package identities, artifact hashes, location categories and finding counts.
Omits paths, raw errors, dependency URLs, arbitrary build metadata and source text.
No feedback is submitted unless --submit is explicitly provided. Submission
requires hosted authentication and uses the configured Megamono service.
Options:
--description=<text> Explain what happened and what you expected
--from-error Include the pre-populated command/error context
--command=<text> Command that failed (normally supplied by the CLI)
--error=<text> Sanitized failure message (normally supplied by the CLI)
--exit-code=<number> Exit code associated with the failure
--submit Submit to the authenticated Megamono service
--json Print the complete redacted payload
--packages=<names> --yalc-store=<directory> --source-root=<repository>
Without --submit, this remains a local report. Nothing is installed, executed,
or written by the command. User descriptions are included as supplied; review
them before submitting.