Add --no-open flag to skip automatic browser launch#59
Merged
Conversation
Adds a --no-open option that prevents Launchy from opening the generated report in a browser. This is useful for CI/CD pipelines and headless environments like Jenkins where browser launch fails. Closes chad#42
This was referenced Jun 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds a
--no-openoption that prevents Launchy from opening the generated report in a browser. This is useful for CI/CD pipelines and headless environments like Jenkins where browser launch fails.Usage
# Generate report without opening browser bule --no-openChanges
no_openconfiguration option (defaults tofalse)--no-openCLI flagCloses #42