Skip to content

Commit 85d58fa

Browse files
Merge pull request #50221 from ShawnKupfer/WB1762a
Update instructions to fork repo
2 parents be1ff75 + d2cae3f commit 85d58fa

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

learn-pr/azure-devops/create-a-build-pipeline/includes/5-set-up-environment.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,5 +31,15 @@ Run a template that sets up your Azure DevOps organization.
3131

3232
1. Once your project is created, go to your Azure DevOps organization in your browser (at `https://dev.azure.com/<your-organization-name>/`) and select the project.
3333

34+
### Fork the repository
35+
36+
If you haven't already, create a fork of the **mslearn-tailspin-spacegame-web** repository.
37+
38+
1. On GitHub, go to the [mslearn-tailspin-spacegame-web](https://github.com/MicrosoftDocs/mslearn-tailspin-spacegame-web) repository.
39+
40+
1. Select **Fork** at the top-right of the screen.
41+
42+
1. Choose your GitHub account as the **Owner**, then select **Create fork**.
43+
3444
> [!IMPORTANT]
3545
> The [Clean up your Azure DevOps environment](/training/modules/create-a-build-pipeline/9-clean-up-environment?azure-portal=true) unit at the end of this module provides important cleanup steps. Cleaning up helps ensure that you don't run out of free build minutes for Microst-hosted agents ([check your usage](/azure/devops/pipelines/licensing/concurrent-jobs#check-the-parallel-jobs-setting-directly)), or GitHub Codespaces [included usage hours and storage](https://docs.github.com/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#monthly-included-storage-and-core-hours-for-personal-accounts) ([charges might apply if you exceed the free tier, so check your usage](https://docs.github.com/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)). Be sure to do the cleanup steps even if you don't complete this module.

0 commit comments

Comments
 (0)