On Sun, Jan 28, 2024 at 8:17 AM Sven Schreiber
<sven.schreiber@fu-berlin.de> wrote:

The point is that the main purpose of bcheck is to handle a bundle with
options supplied by the user (here: "b"). So if the user is happy with
the defaults and doesn't supply such a bundle, I'd argue that bcheck
should simply accept that and do nothing.

OK, it now does so in git, provided that the third argument to bcheck
is not given. (This is an array of names of items that the caller is
required to specify, known as "required-keys" in the bcheck
documentation.) If required-keys is given and the user-bundle is null,
bcheck returns non-zero indicating that the caller's input is
insufficient.