adds code smells and no loc

LuizMacedo · LuizMacedo · commit 5fd208989a72 · 2025-06-23T14:00:40.000-05:00
diff --git a/learn-pr.sln b/learn-pr.sln
@@ -0,0 +1,38 @@
+Microsoft Visual Studio Solution File, Format Version 12.00
+# Visual Studio Version 17
+VisualStudioVersion = 17.5.2.0
+MinimumVisualStudioVersion = 10.0.40219.1
+Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "learn-pr", "learn-pr", "{2131D897-7991-9519-C5EC-8F7F030F7558}"
+EndProject
+Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "azure-devops", "azure-devops", "{47FAB674-FE63-AC99-5926-D31534AB9851}"
+EndProject
+Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "manage-build-dependencies", "manage-build-dependencies", "{A373AFFE-5695-223E-B012-B41198D35D5C}"
+EndProject
+Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "includes", "includes", "{C93D5C04-9046-62E1-DF61-7C5D7F67D42F}"
+EndProject
+Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "6-tailspin.spacegame.web", "learn-pr\azure-devops\manage-build-dependencies\includes\code\6-tailspin.spacegame.web.csproj", "{89B64EBC-FA21-F30E-2A8B-422FE23A1CC6}"
+EndProject
+Global
+	GlobalSection(SolutionConfigurationPlatforms) = preSolution
+		Debug|Any CPU = Debug|Any CPU
+		Release|Any CPU = Release|Any CPU
+	EndGlobalSection
+	GlobalSection(ProjectConfigurationPlatforms) = postSolution
+		{89B64EBC-FA21-F30E-2A8B-422FE23A1CC6}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
+		{89B64EBC-FA21-F30E-2A8B-422FE23A1CC6}.Debug|Any CPU.Build.0 = Debug|Any CPU
+		{89B64EBC-FA21-F30E-2A8B-422FE23A1CC6}.Release|Any CPU.ActiveCfg = Release|Any CPU
+		{89B64EBC-FA21-F30E-2A8B-422FE23A1CC6}.Release|Any CPU.Build.0 = Release|Any CPU
+	EndGlobalSection
+	GlobalSection(SolutionProperties) = preSolution
+		HideSolutionNode = FALSE
+	EndGlobalSection
+	GlobalSection(NestedProjects) = preSolution
+		{47FAB674-FE63-AC99-5926-D31534AB9851} = {2131D897-7991-9519-C5EC-8F7F030F7558}
+		{A373AFFE-5695-223E-B012-B41198D35D5C} = {47FAB674-FE63-AC99-5926-D31534AB9851}
+		{C93D5C04-9046-62E1-DF61-7C5D7F67D42F} = {A373AFFE-5695-223E-B012-B41198D35D5C}
+		{89B64EBC-FA21-F30E-2A8B-422FE23A1CC6} = {C93D5C04-9046-62E1-DF61-7C5D7F67D42F}
+	EndGlobalSection
+	GlobalSection(ExtensibilityGlobals) = postSolution
+		SolutionGuid = {5E06AC6D-71A4-4340-B3DE-F0FFEB92634F}
+	EndGlobalSection
+EndGlobal
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/1-introduction.yml b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/1-introduction.yml
@@ -4,8 +4,8 @@ title: Introduction
 metadata:
   title: Introduction
   description: "Introduction"
-  ms.date: 05/08/2024
-  author: wwlpublish
+  ms.date: 06/23/2025
+  author: LuizMacedo
   ms.author: lumac
   ms.topic: unit
 durationInMinutes: 1
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/10-implement-github-actions-for-ci-cd.yml b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/10-implement-github-actions-for-ci-cd.yml
@@ -4,8 +4,8 @@ title: Implement GitHub Actions for CI/CD
 metadata:
   title: Implement GitHub Actions for CI/CD
   description: "Implement GitHub Actions for CI/CD"
-  ms.date: 05/08/2024
-  author: wwlpublish
+  ms.date: 06/23/2025
+  author: LuizMacedo
   ms.author: lumac
   ms.topic: unit
 durationInMinutes: 40
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/11-knowledge-check.yml b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/11-knowledge-check.yml
@@ -4,8 +4,8 @@ title: Module assessment
 metadata:
   title: Module assessment
   description: "Knowledge check"
-  ms.date: 05/08/2024
-  author: wwlpublish
+  ms.date: 06/23/2025
+  author: LuizMacedo
   ms.author: lumac
   ms.topic: unit
 durationInMinutes: 5
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/12-summary.yml b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/12-summary.yml
@@ -4,8 +4,8 @@ title: Summary
 metadata:
   title: Summary
   description: "Summary"
-  ms.date: 05/08/2024
-  author: wwlpublish
+  ms.date: 06/23/2025
+  author: LuizMacedo
   ms.author: lumac
   ms.topic: unit
 durationInMinutes: 1
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/2-describe-continuous-integration-with-actions.yml b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/2-describe-continuous-integration-with-actions.yml
@@ -4,10 +4,10 @@ title: Describe continuous integration with actions
 metadata:
   title: Describe continuous integration with actions
   description: "Describe continuous integration with actions"
-  ms.date: 05/08/2024
-  author: wwlpublish
+  ms.date: 06/23/2025
+  author: LuizMacedo
   ms.author: lumac
   ms.topic: unit
 durationInMinutes: 3
 content: |
-  [!include[](includes/2-describe-continuous-integration-with-actions.md)]
+  [!include[](includes/2-describe-continuous-integration-with-actions.md)]
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/3-examine-environment-variables.yml b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/3-examine-environment-variables.yml
@@ -4,8 +4,8 @@ title: Examine environment variables
 metadata:
   title: Examine environment variables
   description: "Examine environment variables"
-  ms.date: 05/08/2024
-  author: wwlpublish
+  ms.date: 06/23/2025
+  author: LuizMacedo
   ms.author: lumac
   ms.topic: unit
 durationInMinutes: 3
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/4-share-artifacts-between-jobs.yml b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/4-share-artifacts-between-jobs.yml
@@ -4,8 +4,8 @@ title: Share artifacts between jobs
 metadata:
   title: Share artifacts between jobs
   description: "Share artifacts between jobs"
-  ms.date: 05/08/2024
-  author: wwlpublish
+  ms.date: 06/23/2025
+  author: LuizMacedo
   ms.author: lumac
   ms.topic: unit
 durationInMinutes: 4
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/5-examine-workflow-badges.yml b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/5-examine-workflow-badges.yml
@@ -4,8 +4,8 @@ title: Examine Workflow badges
 metadata:
   title: Examine Workflow badges
   description: "Examine Workflow badges"
-  ms.date: 05/08/2024
-  author: wwlpublish
+  ms.date: 06/23/2025
+  author: LuizMacedo
   ms.author: lumac
   ms.topic: unit
 durationInMinutes: 3
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/6-describe-best-practices-for-creating-actions.yml b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/6-describe-best-practices-for-creating-actions.yml
@@ -4,8 +4,8 @@ title: Describe best practices for creating actions
 metadata:
   title: Describe best practices for creating actions
   description: "Describe best practices for creating actions"
-  ms.date: 05/08/2024
-  author: wwlpublish
+  ms.date: 06/23/2025
+  author: LuizMacedo
   ms.author: lumac
   ms.topic: unit
 durationInMinutes: 2
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/7-mark-releases-git-tags.yml b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/7-mark-releases-git-tags.yml
@@ -4,8 +4,8 @@ title: Mark releases with Git tags
 metadata:
   title: Mark releases with Git tags
   description: "Mark releases with Git tags"
-  ms.date: 05/08/2024
-  author: wwlpublish
+  ms.date: 06/23/2025
+  author: LuizMacedo
   ms.author: lumac
   ms.topic: unit
 durationInMinutes: 2
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/8-create-encrypted-secrets.yml b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/8-create-encrypted-secrets.yml
@@ -4,8 +4,8 @@ title: Create encrypted secrets
 metadata:
   title: Create encrypted secrets
   description: "Create encrypted secrets"
-  ms.date: 05/08/2024
-  author: wwlpublish
+  ms.date: 06/23/2025
+  author: LuizMacedo
   ms.author: lumac
   ms.topic: unit
 durationInMinutes: 3
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/9-use-secrets-workflow.yml b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/9-use-secrets-workflow.yml
@@ -4,8 +4,8 @@ title: Use secrets in a workflow
 metadata:
   title: Use secrets in a workflow
   description: "Use secrets in a workflow"
-  ms.date: 05/08/2024
-  author: wwlpublish
+  ms.date: 06/23/2025
+  author: LuizMacedo
   ms.author: lumac
   ms.topic: unit
 durationInMinutes: 3
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/1-introduction.md b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/1-introduction.md
@@ -4,13 +4,13 @@ This module details continuous integration using GitHub Actions and describes en
 
 After completing this module, students and professionals can:
 
- -  Implement Continuous Integration with GitHub Actions.
- -  Use environment variables.
- -  Share artifacts between jobs and use Git tags.
- -  Create and manage secrets.
+- Implement Continuous Integration with GitHub Actions.
+- Use environment variables.
+- Share artifacts between jobs and use Git tags.
+- Create and manage secrets.
 
 ## Prerequisites
 
- -  Understanding of what DevOps is and its concepts.
- -  Familiarity with version control principles is helpful but isn't necessary.
- -  Beneficial to have experience in an organization that delivers software.
+- Understanding of what DevOps is and its concepts.
+- Familiarity with version control principles is helpful but isn't necessary.
+- Beneficial to have experience in an organization that delivers software.
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/2-describe-continuous-integration-with-actions.md b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/2-describe-continuous-integration-with-actions.md
@@ -25,8 +25,8 @@ jobs:
 
 ```
 
- -  **On:** Specifies what will occur when code is pushed.
- -  **Jobs:** There's a single job called **build.**
- -  **Strategy:** It's being used to specify the Node.js version.
- -  **Steps:** Are doing a checkout of the code and setting up dotnet.
- -  **Run:** Is building the code.
+- :::no-loc text="**On:**"::: Specifies what will occur when code is pushed.
+- :::no-loc text="**Jobs:**"::: There's a single job called **`build`.**
+- :::no-loc text="**Strategy:**"::: It's being used to specify the Node.js version.
+- :::no-loc text="**Steps:**"::: Are doing a checkout of the code and setting up dotnet.
+- :::no-loc text="**Run:**"::: Is building the code.
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/3-examine-environment-variables.md b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/3-examine-environment-variables.md
@@ -2,18 +2,18 @@ When using Actions to create CI or CD workflows, you'll typically need to pass v
 
 ## Built-in environment variables
 
-GitHub provides a series of built-in environment variables. It all has a GITHUB\_ prefix.
+GitHub provides a series of built-in environment variables. It all has a `GITHUB_` prefix.
 
 > [!NOTE]
 > Setting that prefix for your variables will result in an error.
 
 Examples of built-in environment variables are:
 
-**GITHUB\_WORKFLOW** is the name of the workflow.
+**`GITHUB_WORKFLOW`** is the name of the workflow.
 
-**GITHUB\_ACTION** is the unique identifier for the action.
+**`GITHUB_ACTION`** is the unique identifier for the action.
 
-**GITHUB\_REPOSITORY** is the name of the repository (but also includes the name of the owner in owner/repo format)
+**`GITHUB_REPOSITORY`** is the name of the repository (but also includes the name of the owner in owner/repo format)
 
 ## Using variables in workflows
 
@@ -26,8 +26,8 @@ jobs:
             - name: Verify Connection to SQL Server
             - run: node testconnection.js
         env:
-            PROJECT_SERVER: PH202323V
-            PROJECT_DATABASE: HAMaster
+            PROJECT_SERVER: PH202526V
+            PROJECT_DATABASE: HAMain
 
 ```
 
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/4-share-artifacts-between-jobs.md b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/4-share-artifacts-between-jobs.md
@@ -1,6 +1,6 @@
 When using Actions to create CI or CD workflows, you'll often need to pass artifacts created by one job to another.
 
-The most common ways to do it are by using the **upload-artifact** and **download-artifact** actions.
+The most common ways to do it are by using the **`upload-artifact`** and **`download-artifact`** actions.
 
 ## Upload-artifact
 
@@ -52,7 +52,7 @@ You can specify multiple paths:
 
 ```
 
-For more information on this action, see [upload-artifact.](https://github.com/actions/upload-artifact)
+For more information on this action, see [:::no-loc text="upload-artifact.":::](https://github.com/actions/upload-artifact)
 
 ## Download-artifact
 
@@ -68,7 +68,7 @@ There's a corresponding action for downloading (or retrieving) artifacts.
 
 If no path is specified, it's downloaded to the current directory.
 
-For more information on this action, see [download-artifact.](https://github.com/actions/download-artifact)
+For more information on this action, see [:::no-loc text="download-artifact.":::](https://github.com/actions/download-artifact)
 
 ## Artifact retention
 
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/5-examine-workflow-badges.md b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/5-examine-workflow-badges.md
@@ -1,26 +1,25 @@
 Badges can be used to show the status of a workflow within a repository.
 
-They show if a workflow is currently passing or failing. While they can appear in several locations, they typically get added to the README.md file for the repository.
+They show if a workflow is currently passing or failing. While they can appear in several locations, they typically get added to the `README.md` file for the repository.
 
 Badges are added by using URLs. The URLs are formed as follows:
 
-https://github.com/&lt;OWNER&gt;/&lt;REPOSITORY&gt;/actions/workflows/&lt;WORKFLOW\_FILE&gt;/badge.svg
+`https://github.com/&lt;OWNER&gt;/&lt;REPOSITORY&gt;/actions/workflows/&lt;WORKFLOW\_FILE&gt;/badge.svg`
 
 Where:
 
- -  AAAAA is the account name.
- -  RRRRR is the repository name.
- -  WWWWW is the workflow name.
+- `OWNER` is the account name.
+- `REPOSITORY` is the repository name.
+- `WORKFLOW` is the workflow name.
 
 :::image type="content" source="../media/badge-failing-12fd7192.png" alt-text="Screenshot of the Badge failing in a color to represent an error.":::
 
-
 They usually indicate the status of the default branch but can be branch-specific. You do this by adding a URL query parameter:
 
-?branch=BBBBB
+`?branch=BRANCH`
 
 where:
 
- -  BBBBB is the branch name.
+- `BRANCH` is the branch name.
 
 For more information, see: [Adding a workflow status badge](https://docs.github.com/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge).
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/6-describe-best-practices-for-creating-actions.md b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/6-describe-best-practices-for-creating-actions.md
@@ -1,8 +1,8 @@
-It's essential to follow best practices when creating actions:
+It's essential to follow best practices when creating `actions`:
 
- -  Create chainable actions. Don't create large monolithic actions. Instead, create smaller functional actions that can be chained together.
- -  Version your actions like other code. Others might take dependencies on various versions of your actions. Allow them to specify versions.
- -  Provide the **latest** label. If others are happy to use the latest version of your action, make sure you provide the **latest** label that they can specify to get it.
- -  Add appropriate documentation. As with other codes, documentation helps others use your actions and can help avoid surprises about how they function.
- -  Add details **action.yml** metadata. At the root of your action, you'll have an **action.yml** file. Ensure it has been populated with author, icon, expected inputs, and outputs.
- -  Consider contributing to the marketplace. It's easier for us to work with actions when we all contribute to the marketplace. Help to avoid people needing to relearn the same issues endlessly.
+- Create chainable `actions`. Don't create large monolithic `actions`. Instead, create smaller functional `actions` that can be chained together.
+- Version your `actions` like other code. Others might take dependencies on various versions of your `actions`. Allow them to specify versions.
+- Provide the **`latest`** label. If others are happy to use the latest version of your `action`, make sure you provide the **`latest`** label that they can specify to get it.
+- Add appropriate documentation. As with other codes, documentation helps others use your `actions` and can help avoid surprises about how they function.
+- Add details **`action.yml`** metadata. At the root of your `action`, you'll have an **`action.yml`** file. Ensure it has been populated with author, icon, expected inputs, and outputs.
+- Consider contributing to the marketplace. It's easier for us to work with `actions` when we all contribute to the marketplace. Help to avoid people needing to relearn the same issues endlessly.
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/7-mark-releases-git-tags.md b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/7-mark-releases-git-tags.md
@@ -1,15 +1,13 @@
-Releases are software iterations that can be packed for release.
+`Releases` are software iterations that can be packed for release.
 
-In Git, releases are based on Git tags. These tags mark a point in the history of the repository. Tags are commonly assigned as releases are created.
+In Git, `releases` are based on Git tags. These tags mark a point in the history of the repository. Tags are commonly assigned as `releases` are created.
 
 :::image type="content" source="../media/git-release-tag-28ff3ca4.png" alt-text="Screenshot of Git Release Tag creation page.":::
 
-
 Often these tags will contain version numbers, but they can have other values.
 
 Tags can then be viewed in the history of a repository.
 
 :::image type="content" source="../media/tag-history-ed9cbbd4.png" alt-text="Screenshot of the Git release tag page showing the tag information.":::
 
-
-For more information on tags and releases, see: [About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases).
+For more information on tags and `releases`, see: [About :::no-loc text="releases":::](https://docs.github.com/repositories/releasing-projects-on-github/about-releases).
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/8-create-encrypted-secrets.md b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/8-create-encrypted-secrets.md
@@ -1,21 +1,20 @@
-Actions often can use secrets within pipelines. Common examples are passwords or keys.
+Actions often can use `secrets` within pipelines. Common examples are passwords or keys.
 
-In GitHub actions, It's called **Secrets**.
+In GitHub actions, It's called **`Secrets`**.
 
-## Secrets
+## `Secrets`
 
-Secrets are similar to environment variables but encrypted. They can be created at two levels:
+`Secrets` are similar to environment variables but encrypted. They can be created at two levels:
 
- -  Repository
- -  Organization
+- Repository
+- Organization
 
-If secrets are created at the organization level, access policies can limit the repositories that can use them.
+If `secrets` are created at the organization level, access policies can limit the repositories that can use them.
 
-## Creating secrets for a repository
+## Creating `secrets` for a repository
 
-To create secrets for a repository, you must be the repository's owner. From the repository **Settings**, choose **Secrets**, then **New Secret**.
+To create `secrets` for a repository, you must be the repository's owner. From the repository **`Settings`**, choose **`Secrets`**, then **`New Secret`**.
 
 :::image type="content" source="../media/new-secret-5ba1255e.png" alt-text="Screenshot of new secret creation from settings.":::
 
-
-For more information on creating secrets, see [Encrypted secrets](https://docs.github.com/actions/security-guides/encrypted-secrets).
+For more information on creating `secrets`, see [Encrypted secrets](https://docs.github.com/actions/security-guides/encrypted-secrets).
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/9-use-secrets-workflow.md b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/includes/9-use-secrets-workflow.md
@@ -1,4 +1,4 @@
-Secrets aren't passed automatically to the runners when workflows are executed. To make a secret available to an action, you must set the secret as an input or environment variable in the workflow file. To accomplish this, you can use the secrets context as illustrated in following example:<br>
+Secrets aren't passed automatically to the runners when workflows are executed. To make a secret available to an action, you must set the secret as an input or environment variable in the workflow file. To accomplish this, you can use the secrets context as illustrated in following example:
 
 ```YAML
 steps:
@@ -28,7 +28,7 @@ It's important to follow this approach, which minimizes the risk of their accide
 
 ## Using secrets in if: conditionals
 
-Since secrets can't be directly referenced in if: conditionals, as a workaround, consider setting secrets as job-level environment variables, then referencing the environment variables to conditionally run steps in the job, as in the following example:
+Since secrets can't be directly referenced in `if:` conditionals, as a workaround, consider setting secrets as job-level environment variables, then referencing the environment variables to conditionally run steps in the job, as in the following example:
 
 ```YAML
 name: Run a step if a secret has been set
@@ -49,4 +49,4 @@ jobs:
 
 Workflows can use up to 100 secrets, regardless of their location. Secrets are limited to 48 KB in size. To use secrets that are larger than 48 KB, you can use a workaround to store secrets in your repository and save the decryption passphrase as a secret on GitHub. For details regarding this procedure, refer to [Storing large secrets](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#storing-large-secrets) topic in GitHub documentation.
 
-Note that with the exception of GITHUB\_TOKEN, secrets aren't passed to the runner when a workflow is triggered from a forked repository.<br>
+Note that with the exception of `GITHUB_TOKEN`, secrets aren't passed to the runner when a workflow is triggered from a forked repository.
diff --git a/learn-pr/wwl-azure/learn-continuous-integration-github-actions/index.yml b/learn-pr/wwl-azure/learn-continuous-integration-github-actions/index.yml
