actions/importer-labs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update azure_devops/valet-forecast-lab.md

Browse Source 
Co-authored-by: Liam Neville <[email protected]>
This commit is contained in:
j-dunham
2022-08-31 14:07:15 -04:00
committed by GitHub
co-authored by Liam Neville
parent b868afa5a1
commit 0cde23eb45
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
azure_devops/valet-forecast-lab.md
+1 -1
View File
@@ -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. 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.__ 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.__ 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: Using these answers our command becomes:
``` ```