From 0cde23eb45fe9ef34e40c7106b8b31985b159787 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Wed, 31 Aug 2022 14:07:15 -0400 Subject: [PATCH] Update azure_devops/valet-forecast-lab.md Co-authored-by: Liam Neville --- azure_devops/valet-forecast-lab.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/azure_devops/valet-forecast-lab.md b/azure_devops/valet-forecast-lab.md index a079465..dbccbe1 100644 --- a/azure_devops/valet-forecast-lab.md +++ b/azure_devops/valet-forecast-lab.md @@ -15,7 +15,7 @@ In this lab we will use the `forecast` command to forecast potential GitHub Acti Before we can run the forecast we need to answer a few questions so we can construct the correct command. 1) What is the date we want to start forecasting from? __2022-03-02. This should be a date that will give enough data to get a good understanding of the typical usage.__ 2) Where do we want to store the results? __./tmp/forecast_reports. This can be any valid path on the system, but for simplicity it is recommend to use a directory in the root of the codespace workspace.__ -3) What project do we want to run the forecast for? __ValetBootStrap. This is the default project name for the labs, if you choose a different name when setting up the lab environment you should use that.__ +3) What project do we want to run the forecast for? __ValetBootStrap. This is the default project name for the labs, if you choose a different name when setting up the lab environment you should use that.__ Using these answers our command becomes: ```