When you run "spk build", you can specify an .spk.yaml file, but if you neglect to do so and there is only one .spk.yaml in the current directory, it will just use it. This is a great default behvior!
But many other spk commands don't do this. For example, "spk mkb", even though it conceptually is a minor variant of build, will give an error about missing arguments. This is needless friction.
All commands that expect an .spk.yaml file should work like build, just working as expected if there's only one .spk.yaml file in the cwd.
When you run "spk build", you can specify an .spk.yaml file, but if you neglect to do so and there is only one .spk.yaml in the current directory, it will just use it. This is a great default behvior!
But many other spk commands don't do this. For example, "spk mkb", even though it conceptually is a minor variant of build, will give an error about missing arguments. This is needless friction.
All commands that expect an .spk.yaml file should work like build, just working as expected if there's only one .spk.yaml file in the cwd.