Add support for a new 'validate' command - #365
Merged
Merged
Conversation
This command will return a 0 for an expected stable underlying stack and 1 for an unstable.
superm1
force-pushed
the
validate-command
branch
from
February 23, 2026 05:28
ef40d99 to
3904ca9
Compare
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
2 participants
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.
This command will return a 0 for an expected stable underlying stack and 1 for an unstable.
When running explicitly on my machine:
The sanity check also implicitly runs for all commands but will only display errors.
The idea is that higher level software can call
flm validateand examine the return code to decide whetherflmshould be usable.