bazel-contrib / bazel-contrib/buildtools

Buildifier - Create a more sensible "flags" system and experimental features

Open
#1,440 0 comments 0 reactions 0 assignees View on GitHub
P3
Dominant language
Go
Stars
1.2k
Forks
471
Avg merge
2d 22h
Merged PRs (30d)
13

Description

Many PRs in this repository fall into specific categories, e.g. implementation of warnings / formatting changes which are not possible to enable by default, or just resolving very specific needs.

Right now there's no branching or flags-system for implementing these besides submitting them as part of core buildifier / buildozer. If we defined a separate directory and interface for experimental warnings we could simplify the process of getting custom checks merged, and through this enable better support for buildtools users.

Contributor guide

Open the contributing guide

Research direction

The issue does not identify files, tests, or entry points. Start by mapping how Buildifier and Buildozer currently register and enable warnings, then review existing warning-related changes and interfaces. Done means an agreed separate directory and interface exists for experimental warnings, with a clear way to enable them without changing core defaults.

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
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.