Buf(1)

πŸ“¦
version 1.75.0 Β· 3 versions
, in arch rolling

Hey bestie, welcome to Buf(1) β€” the manual page for buf-config-ls-lint-rules. It’s short, it’s sweet, and it’s here to list lint rules. πŸ’…

🌸 NAME 🌸

  • buf-config-ls-lint-rules β€” List lint rules. That’s the name, and that’s the whole assignment. ✨

πŸŽ€ SYNOPSIS πŸŽ€

Run it exactly like this:

buf config ls-lint-rules [flags]

πŸ’– DESCRIPTION πŸ’–

List lint rules β€” literally what it says on the tin. This command lists lint rules. No cap. πŸ¦‹

✨ OPTIONS ✨

  • --config="" β€” the buf.yaml file or data to use for configuration. The page also says: --configured-only must be set. iykyk.
  • --configured-only[=false] β€” list rules that are configured instead of listing all available rules. So it’s the β€œonly the chosen ones” mode.
  • --format="text" β€” the format to print rules as. Must be one of [text,json]. Pick your output vibe.
  • -h, --help[=false] β€” help for ls-lint-rules. Classic help behavior, iconic as always.
  • --include-deprecated[=false] β€” also print deprecated rules. Has no effect if --configured-only is set. Important caveat, bestie!
  • --module-path="" β€” the path to the specific module to list configured rules for as specified in the buf.yaml. If the buf.yaml has more than one module defined, this must be set. --configured-only must be set. Multi-module besties, pay attention.
  • --version="" β€” list all the rules for the given configuration version. By default, the version in the buf.yaml in the current directory is used, or the latest version otherwise (currently v2). Cannot be set if --configured-only is set. Must be one of [v1beta1,v1,v2]. Version check, but make it fashion.

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

These come from the parent command, and they still serve:

  • --debug[=false] β€” turn on debug logging (env BUF_DEBUG). Spicy little debug mode.
  • --log-format="color" β€” the log format text,color,json ⟨env BUF_LOG_FORMAT⟩. You can go text, color, or json.
  • --timeout=0s β€” the duration until timing out, setting it to 0 means no timeout (env BUF_TIMEOUT). Zero means no timeout, bestie β€” the clock simply says β€œnot today.”

πŸ”₯ SEE ALSO πŸ”₯

  • buf-config(1) β€” the parent-command lore lives there. 🫢

πŸ‘‘ HISTORY πŸ‘‘

  • 2026-10-22 β€” Auto generated by spf13/cobra. The robots wrote this one, and honestly? Slay. πŸ€–βœ¨

πŸ’– That’s the whole Buf(1) page, bestie β€” auto generated by spf13/cobra, dated 2026-10-22. Go list those lint rules and have the best day. 🫢

πŸ“¦ where this page comes from