bazelbuild/bazel

user.bazelrc or .bazelrc.user?

Open

#28,839 建立於 2026年2月28日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)Java (25,384 star) (4,465 fork)batch import
P2help wantedteam-Documentationteam-OSStype: documentation (cleanup)

描述

Page link:

No response

Problem description (include actual vs expected text, if applicable):

Bazel best practices recommends

try-import %workspace%/user.bazelrc

But rules-template has

try-import %workspace%/.bazelrc.user

Which is it? It would be nice to be consistent, for users to be able to override project flags in a predictable location.

Where do you see this issue? (include link to specific section of the page, if applicable)

No response

Any other information you'd like to share?

No response

貢獻者指南

技術棧
無
領域
build systemdeveloper experiencedocumentation
議題類型
documentation
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
1
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
familiarity with Bazel .bazelrc files
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
90
研究方向
The issue points out an inconsistency between Bazel's official best practices documentation (recommending `%workspace%/user.bazelrc`) and the rules template repository (using `%workspace%/.bazelrc.user`). To resolve, investigate both sources: the Bazel documentation at https://bazel.build/configure/best practices#bazelrc file and the rules template `.bazelrc` at https://github.com/bazel contrib/rules template/blob/main/.bazelrc. Determine which filename is the intended standard and update the inconsistent file. There are no linked PRs or assignees, so this is available for a first timer.