Initialise m_bare flag in init subcommand - #56
Merged
JohanMabille merged 1 commit intoNov 27, 2025
Merged
JohanMabille merged 1 commit into
JohanMabille merged 1 commit into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
JohanMabille
approved these changes
Nov 27, 2025
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
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.
Initialise init_subcommand.m_bare boolean flag as is done with other boolean flags passed to cli11 subcommands. This turned out to cause a problem with the emscripten-forge build, depending on the compiler flags.