Skip to content

REPORT_OUTPUT_FOLDER: none creates a folder named "none" #2108

@bittner

Description

@bittner

Describe the bug
When I (use a container image to) run megalinter locally, I want it to not create reports. Unfortunately, setting REPORT_OUTPUT_FOLDER to none doesn't help as documented, instead it makes megalinter create a folder named "none".

To Reproduce
Steps to reproduce the behavior:

  1. Create a configuration file .mega-linter.yml.
  2. Add REPORT_OUTPUT_FOLDER: none as a configuration setting in that file.
  3. Run megalinter (e.g. via a container image as below).
  4. A folder named "none" is created, which contains the megalinter reports.
docker run --rm -v $PWD:$PWD -e DEFAULT_WORKSPACE=$PWD oxsecurity/megalinter-documentation:v6

Expected behavior
No folder is created. No reports are written to the file system.

Additional context
Related: Is there a typo in the documentation of REPORT_OUTPUT_FOLDER or what does that sentence mean?

- Send `none` to not generate reports
+ Set to `none` to not generate reports

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingnostaleThis issue or pull request is not stale, keep it open

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions