Skip to content

Conversation

@benjaminp
Copy link
Collaborator

According to https://docs.google.com/document/d/1L1JFgjpZ7SrBinb24DC_5nTIELeYDacikcme-YcA7xs/edit?tab=t.0#heading=h.cy0m49ne5key, defs.bzl is legacy. So, don't advise creating one in new rule sets.

@github-actions github-actions bot added team-Documentation Documentation improvements that cannot be directly linked to other team labels awaiting-review PR is awaiting review from an assigned reviewer labels Dec 20, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation for deploying Bazel rules to recommend using separate .bzl files for each symbol, instead of a single defs.bzl file. This change aligns with modern Bazel best practices for better granularity and modularity. The changes in site/en/rules/deploying.md are clear and accurately reflect this new recommendation. The pull request improves the documentation and promotes better rule-writing practices.

@iancha1992 iancha1992 added the team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website label Dec 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting-review PR is awaiting review from an assigned reviewer team-Documentation Documentation improvements that cannot be directly linked to other team labels team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants