From f028f97e8cc830ca5bfdded4036cfe99492ca343 Mon Sep 17 00:00:00 2001 From: keyonghan <54558023+keyonghan@users.noreply.github.com> Date: Tue, 28 Feb 2023 17:21:56 -0800 Subject: [PATCH] update doc (#113778) Update recipes doc with correct parameters --- dev/bots/README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/dev/bots/README.md b/dev/bots/README.md index a610b579a1..bfed67e4ef 100644 --- a/dev/bots/README.md +++ b/dev/bots/README.md @@ -73,9 +73,8 @@ The typical cycle for editing a recipe is: the existing expected output to match the new output. Verify completely new test cases by altering the `GenTests` method of the recipe. The recipe is required to have 100% test coverage. -4. Run `led get-builder 'luci.flutter.staging:BUILDER_NAME' | led edit -p 'revision="GIT_HASH"' | led edit-recipe-bundle | led launch`, where `BUILDER_NAME` is the builder name (e.g. `Linux Engine`), and - `GIT_HASH` is the hash to build (which is important for the engine but not - for the framework). +4. Run `led get-builder 'luci.flutter.staging:BUILDER_NAME' | led edit -pa git_ref='refs/pull//head' | led edit -pa git_url='https://github.com/flutter/' | led edit-recipe-bundle | led launch`, where `BUILDER_NAME` is the builder name (e.g. `Linux Engine`), and + `git_ref`/`git_url` is the ref/url of the intended changes to build. * If `led` fails, ensure that your `depot_tools` checkout is up to date. 5. To submit a CL, you need a local branch first (`git checkout -b [some branch name]`). 6. Upload the patch (`git commit`, `git cl upload`), and open the outputted URL to the CL.