From ebd4416defdbd006698c1f4c39b2ced0b5641e57 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Thu, 21 May 2026 20:26:24 +0000 Subject: [PATCH] chore: update documentation from upstream Bazel repo [skip ci] Synchronized pre-converted MDX files from upstream Bazel repository. --- extending/rules.mdx | 4 ++++ reference/command-line-reference.mdx | 6 ------ upstream | 2 +- 3 files changed, 5 insertions(+), 7 deletions(-) diff --git a/extending/rules.mdx b/extending/rules.mdx index 8a4efe20..2fedbf21 100644 --- a/extending/rules.mdx +++ b/extending/rules.mdx @@ -534,6 +534,10 @@ def _example_library_impl(ctx): ] ``` +When defining a provider, it is strongly recommended to specify the `fields` +parameter. This creates a *schemaful provider*, which allows Bazel to store +provider instances more compactly. + ##### Custom initialization of providers It's possible to guard the instantiation of a provider with custom diff --git a/reference/command-line-reference.mdx b/reference/command-line-reference.mdx index deabe770..c1ef0ae7 100644 --- a/reference/command-line-reference.mdx +++ b/reference/command-line-reference.mdx @@ -4307,12 +4307,6 @@ Options that affect the verbosity, format or location of logging: Tags: [`affects_outputs`](#effect_tag_AFFECTS_OUTPUTS) -`--remote_analysis_json_log=` default: see description -: If set, a JSON file is written to this location that contains a detailed log of the behavior of remote analysis caching. It's interpreted as a path relative to the current working directory. - - Tags: - [`bazel_monitoring`](#effect_tag_BAZEL_MONITORING) - `--remote_print_execution_messages=` default: "failure" : Choose when to print remote execution messages. Valid values are `failure`, to print only on failures, `success` to print only on successes and `all` to print always. diff --git a/upstream b/upstream index 10efaccb..468d1bdb 160000 --- a/upstream +++ b/upstream @@ -1 +1 @@ -Subproject commit 10efaccb1d885a37ece9b9e32e3f99bc7c513368 +Subproject commit 468d1bdb883fb34a210bd82d6f53f1ceb747a025