Buf(1)
π
Buf(1) β the buf breaking page, bestie edition π
okay so this is Buf(1), and we're zooming straight in on buf breaking. it's the vibe-check command. the "did u just break my API" command. iconic behavior only. β¨
πΈ NAME πΈ
buf-breaking β verify no breaking changes have been made π«Ά
like, literally just making sure u didn't ruin everything. no cap.
β SYNOPSIS β
buf breaking --against [flags]
π¦ DESCRIPTION π¦
bestie. this command makes sure that the location has no breaking changes compared to the location. yes. that's the whole assignment. π
the first argument is the source, module, or image to check for breaking changes, and it must be one of format [binpb,dir,git,json,mod,protofile,tar,txtpb,yaml,zip]. if u don't pass an argument at all, it just defaults to "." β like, it'll just look at where u already are. main character energy tbh. π
β¨ OPTIONS β¨
--against=""β Required, except if--against-registryis set. this is the source, module, or image to check against. must be one of format[binpb,dir,git,json,mod,protofile,tar,txtpb,yaml,zip]. it's giving "who am i comparing myself to" π--against-config=""β thebuf.yamlfile or data to use to configure the against source, module, or image. yes, the against side gets its own config. she's got her own little setup. π--against-registry[=false]β run breaking checks against the latest commit on the default branch in the registry. all modules in the input must have a name configured, otherwise this will fail. and if a remote module is not found with the configured name, then this will also fail. also also β this cannot be set with--against. pick a lane, bestie. π--config=""β thebuf.yamlfile or data to use for configuration--disable-symlinks[=false]β do not follow symlinks when reading sources or configuration from the local filesystem. by default, symlinks are followed in this CLI, but never followed on the Buf Schema Registry. so like, know the difference, ok? π§--error-format="text"β the format for build errors or check violations printed to stdout. must be one of[text,json,msvs,junit,github-actions,gitlab-code-quality]--exclude-imports[=false]β exclude imports from breaking change detection. we're not checking the plus-ones today. βοΈ--exclude-path=[]β exclude specific files or directories, e.g."proto/a/a.proto","proto/a". if specified multiple times, the union is taken-h,--help[=false]β help for breaking π«Ά (the little helper)--limit-to-input-files[=false]β only run breaking checks against the files in the input. when set, the against input contains only the files in the input. overrides--pathβ yeah she said what she said. π₯--path=[]β limit to specific files or directories, e.g."proto/a/a.proto","proto/a". if specified multiple times, the union is taken
π OPTIONS INHERITED FROM PARENT COMMANDS π
these come from upstairs. the parent commands. we love a family heirloom. π
--debug[=false]β turn on debug logging (envBUF_DEBUG)--log-format="color"β the log format text,color,json β¨envBUF_LOG_FORMATβ©--timeout=0sβ the duration until timing out, setting it to0means no timeout (envBUF_TIMEOUT). literally "we have all the time in the world" energy. π
π SEE ALSO π
buf(1) β go say hi to the main page, she misses u π«Ά
π HISTORY π
2026-10-22 Auto generated by spf13/cobra
fr fr: if--againstisn't set and--against-registryisn't set either, that's a problem. and if u try to use both--againstand--against-registrytogether β nope, not allowed. π
and that's the page!! auto generated by spf13/cobra, dated 2026-10-22 β a little robot wrote this for u with love, slay, periodt. πβ¨π
π¦ where this page comes from
- arch rolling: buf 1.75.0-1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms