From c9bf144f6679a573566ab942ef0db0c32a515140 Mon Sep 17 00:00:00 2001 From: Mergen Nachin Date: Tue, 15 Oct 2024 14:29:29 -0700 Subject: [PATCH] Instruct people to clone viable/strict as opposed to main Summary: In the main branch of the documentation, let's ask people to use 'viable/strict' instead. Differential Revision: D64375880 --- docs/source/getting-started-setup.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/source/getting-started-setup.md b/docs/source/getting-started-setup.md index e8a2b4530d9..f2f98d65638 100644 --- a/docs/source/getting-started-setup.md +++ b/docs/source/getting-started-setup.md @@ -80,7 +80,9 @@ Alternatively, if you would like to experiment with ExecuTorch quickly and easil ```bash # Clone the ExecuTorch repo from GitHub - git clone https://github.com/pytorch/executorch.git + # 'main' branch is the primary development branch where you see the latest changes. + # 'viable/strict' contains all of the commits on main that pass all of the necessary CI checks. + git clone --branch viable/strict https://github.com/pytorch/executorch.git cd executorch # Update and pull submodules