From fcb7015025b4dc8f2ca92fc23b2e613b527a334c Mon Sep 17 00:00:00 2001 From: 4meta5 Date: Mon, 18 Dec 2023 19:32:55 -0500 Subject: [PATCH] fmt --- docs/modules/ROOT/pages/guides/weights_fees.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/modules/ROOT/pages/guides/weights_fees.adoc b/docs/modules/ROOT/pages/guides/weights_fees.adoc index e49a9fb..46385c8 100644 --- a/docs/modules/ROOT/pages/guides/weights_fees.adoc +++ b/docs/modules/ROOT/pages/guides/weights_fees.adoc @@ -22,7 +22,7 @@ Production runtimes should never set `WeightInfo = ()` in production because thi ``` cargo build --features runtime-benchmarks ``` - +[start=2] . Run the benchmarking command and write its output to the runtime. Here is the command via bash script: ``` #!/bin/sh @@ -44,7 +44,7 @@ for pallet_name in $pallets; do --output ./runtime/src/weights/$pallet_name.rs done ``` - +[start=3] . Automate the benchmarking pipeline. The first step may be automated by enforcing the command in the CI. The second step may be automated by integrating a benchmarking github bot. For an example, see https://github.com/paritytech/command-bot[Parity's Command Bot]. == More Reading