Description of the bug:

bazel help flags-as-proto incorrectly reports allows_multiple: false for --bazelrc

Which category does this issue belong to?

CLI

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

wget https://raw.githubusercontent.com/bazelbuild/bazel/refs/tags/8.0.0/src/main/protobuf/bazel_flags.proto
bazel help flags-as-proto | base64 --decode | protoc --decode bazel_flags.FlagCollection bazel_flags.proto

outputs:

[ other options... ]

flag_infos {
  name: "bazelrc"
  has_negative_flag: false
  documentation: "The location of the user .bazelrc file containing default values of Bazel options. /dev/null indicates that all further `--bazelrc`s will be ignored, which is useful to disable the search for a user rc file, e.g. in release builds.\nThis option can also be specified multiple times.\nE.g. with `--bazelrc=x.rc --bazelrc=y.rc --bazelrc=/dev/null --bazelrc=z.rc`,\n  1) x.rc and y.rc are read.\n  2) z.rc is ignored due to the prior /dev/null.\nIf unspecified, Bazel uses the first .bazelrc file it finds in the following two locations: the workspace directory, then the user\'s home directory.\nNote: command line options will always supersede any option in bazelrc."
  commands: "startup"
  allows_multiple: false
  effect_tags: "CHANGES_INPUTS"
  documentation_category: "BAZEL_CLIENT_OPTIONS"
  requires_value: true
}

[ other options... ]

The allows_multiple: false directly contradicts the documentation two lines above it, claiming that "This option can also be specified multiple times."

Which operating system are you running Bazel on?

Debian trixie

What is the output of bazel info release?

release 8.0.0

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

[email protected]:buildbuddy-io/buildbuddy.git
63fdbc967bd6b7af19c70c66ae01e3e353d91346

If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

No response

Have you found anything relevant by searching the web?

I don't think there's anything that searching the web can help with here.

Any other information, logs, or outputs that you want to share?

No, I think what I've provided should be sufficient.