Buf(1)

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

πŸ’… Buf(1) β€” like, the buf-plugin-push manual, bestie

Okay so first things first: this is Buf(1), the manual page for buf-plugin-push, and I'm gonna walk you through it like we're texting at 2am. Grab a snack. πŸ“


✨ NAME ✨

buf-plugin-push β€” push a check plugin to a registry 🫢


🌸 SYNOPSIS 🌸

buf plugin push  [flags]

That's it. That's the whole vibe. Command, then flags. Slay.


πŸ¦‹ DESCRIPTION πŸ¦‹

The first argument is the plugin full name in the format .

Yes, that's literally what it says, and yes, the format part is just a lonely little period in the original β€” I'm not gonna make up a format for you, that's not my job, my job is to be honest and iconic. πŸ’€


πŸŽ€ OPTIONS πŸŽ€

Okay this is the part you actually came for. Every flag, no skipping, we do not leave the group chat on read.

  • --binary="" β€” the path to the Wasm binary file you're pushing. Give it the file, bestie. ✨
  • --create[=false] β€” create the plugin if it doesn't already exist. Defaults to creating a private plugin on the BSR when --create-visibility isn't set. Heads up though: it must be used with --create-type. πŸ”₯
  • --create-type="" β€” the plugin's type setting, if it gets created. Can only be set alongside --create. Must be one of [check] β€” that's the whole list, it's a very exclusive club. πŸ‘‘
  • --create-visibility="private" β€” the module's visibility setting, if it gets created. Can only be set with --create. Must be one of [public,private]. Default is private, so it's giving very "close friends story" energy. πŸ™ˆ
  • -h, --help[=false] β€” help for push. The classic. πŸŽ€
  • --label=[] β€” associate the label with the plugins pushed. Can be used multiple times, so stack 'em like stickers on a laptop. ⭐
  • --source-control-url="" β€” the URL for viewing the source code of the pushed plugins (e.g. the specific commit in source control). Receipts, basically. 🧚

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

These ones come down from the parent command β€” not this page's problem, but they're here so you're not confused later. πŸ’œ

  • --debug[=false] β€” turn on debug logging (env BUF_DEBUG). For when you're in your detective era. πŸ”
  • --log-format="color" β€” the log format: text, color, json ⟨env BUF_LOG_FORMAT⟩. Pick your aesthetic. 🎨
  • --timeout=0s β€” the duration until timing out; setting it to 0 means no timeout (env BUF_TIMEOUT). Zero means forever, no cap. 😭

πŸ‘‘ SEE ALSO πŸ‘‘

buf-plugin(1) β€” go read that one too, it's the parent and it's literally the main character. 🫢


πŸ’€ HISTORY πŸ’€

2026-10-22 β€” Auto generated by spf13/cobra.

Not me being a whole auto-generated manual page. Ngl it ate. πŸ’…


Fr fr though: every flag above is verbatim, defaults included β€” --create-visibility really does default to "private", and --create really does refuse to work without --create-type. Don't come for me if you skip the pairing. 🫢

Okay that's the whole page, mwah πŸ’– β€” this was Buf(1) (manual name folded in near the top, as promised πŸŽ€), auto generated by spf13/cobra and dated 2026-10-22, and that's the sign-off. Byeeee βœ¨πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from