bazel-contrib / bazel-contrib/buildtools
Buildozer - allow overriding build file names
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 471
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 13
Description
There's a few different use cases where it would be useful to specify custom file names which are identified and processed by Buildozer.
This could for instance be enabled via a command line flag.
Note: File names are referenced in a number of places to for instance determine whether a file should be processed as `.bzl` or a `BUILD` file, so this change would need to be done holistically, making sure that all the behaviors which depend on the file name are supported, and that overriding the default file names does not produce unexpected side effects.
(Based to a large extent on PR #168)
Contributor guide
Research direction
Start by tracing Buildozer's file-name detection and the command-line flag entry points. Identify every behavior that distinguishes .bzl and BUILD files, then verify that custom names are handled consistently without unexpected side effects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100