Skip to content

Conversation

@canndrew
Copy link
Contributor

Builds on #1

Print help/usage info if run without a subcommand instead of printing Execution failed: Subcommand not found:

@apoelstra
Copy link
Contributor

Needs rebase now (probably best to rebase on #6 now so we get CI)

@apoelstra
Copy link
Contributor

Can you rebase on #6? Now it will require updating the CLI regression tests, which is a nice test of them. (In general, don't worry about breaking those tests -- the point of them is so that we can do a diff of them before releases, but for now we don't care about stability because the tool was basically just created and has no users.)

Print the help/usage info if run without a subcommand instead of
printing a bad error message.
@canndrew canndrew force-pushed the 2025-06-cli-require-subcommand branch from 52eac61 to a79d139 Compare June 26, 2025 20:22
Copy link
Contributor

@apoelstra apoelstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK a79d139; successfully ran local tests; nice!

@apoelstra apoelstra merged commit 09aee37 into BlockstreamResearch:master Jun 27, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants