Make it possible to ignore `buf.yaml` in the `buf_format` rule

Open
#154 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Domain
build-system

Research direction

Start by locating the implementation and tests for the buf_format Bazel rule, then trace how it reads buf.yaml. Compare the requested options—using a custom config or ignoring the existing config—and choose the behavior that lets the rule format all repository proto files. Done means the selected option is configurable and covered by tests.

Written by the indexing model from the issue text.

Description

I have a buf.yaml file in the repo, but it only lists some of the proto files/dirs (for unrelated reasons). I'd like to use the buf_format Bazel rule to format all the proto files in the repo, not only what is listed in buf.yaml. There is currently no way to do what I'd like to do.

Would be good to make it possible to either specify a custom config or ignore the existing config (my preferred option). Or maybe both.

Thank you!

Dominant language
Starlark
Stars
63
Forks
41
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bufbuild/rules_buf

All issues in bufbuild/rules_buf

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.