LironEr

> > I tried to replicate the bug with cypress v10 and everything works as expected. > > Can you try to upgrade? > > Okay, but did you try...

I tried to replicate the bug with cypress v10 and everything works as expected. Can you try to upgrade?

Currently no, because we cant add context per suite/spec file. Related issues: https://github.com/adamgruber/mochawesome-report-generator/issues/124 https://github.com/adamgruber/mochawesome-report-generator/issues/150

> Currently no, because we cant add context per suite/spec file. Related issues: [adamgruber/mochawesome-report-generator#124](https://github.com/adamgruber/mochawesome-report-generator/issues/124) [adamgruber/mochawesome-report-generator#150](https://github.com/adamgruber/mochawesome-report-generator/issues/150) @mudit94 unfortunately no

Each output will accept ``` "always" / "on-failure" / "off" ``` default: ```json "reportOutput": [ [ "github", { "checkRun": "off", "commitStatus": "always", "prComment": "always" } ] ] ``` @tleunen what...

Feature available in [[email protected]](https://github.com/LironEr/bundlemon/releases/tag/bundlemon%402.0.0-rc.1)

Should be fixed in [v3.2.3](https://github.com/LironEr/cypress-mochawesome-reporter/releases/tag/v3.2.3). Thank you for reporting this issue (:

@luqy maybe you have other issue, please provide an example so I can take a look.

Please provide more information, add log file, add your full config and state the correct `cypress-mochawesome-reporter` Even better, create a repo and describe the steps to reproduce the bug.

Regarding the warning option: > The Commit status API allows external services to mark commits with an error, failure, pending, or success state https://docs.github.com/en/rest/commits/statuses#about-the-commit-statuses-api ------ > Potentially making the default...