Updated links

Author: GeekTrainer

content/0-setup.md

@@ -1,6 +1,6 @@
 # Workshop setup
 
-| [← Modern DevOps with GitHub][walkthrough-previous] | [Next: Enable Code Scanning →][walkthrough-next] |
+| [← Modern DevOps with GitHub][previous] | [Next: Enable Code Scanning →][next] |
 |:-----------------------------------|------------------------------------------:|
 
 To complete this workshop you will need to create a repository with a copy of the contents of this repository. While this can be done by [forking a repository][fork-repo], the goal of a fork is to eventually merge code back into the original (or upstream) source. In our case we want a separate copy as we don't intend to merge our changes. This is accomplished through the use of a [template repository][template-repo]. Template repositories are a great way to provide starters for your organization, ensuring consistency across projects.
@@ -22,13 +22,14 @@ Let's create the repository you'll use for your workshop.
 In a few moments a new repository will be created from the template for this workshop!
 
 ## Summary and next steps
-You've now created the repository you'll use for this workshop! Next let's [enable Code Scanning][walkthrough-next] to secure the code we write.
+You've now created the repository you'll use for this workshop! Next let's [enable Code Scanning][next] to secure the code we write.
 
-| [← Modern DevOps with GitHub][walkthrough-previous] | [Next: Enable Code Scanning →][walkthrough-next] |
+| [← Modern DevOps with GitHub][previous] | [Next: Enable Code Scanning →][next] |
 |:-----------------------------------|------------------------------------------:|
 
+[next]: ./1-code-scanning.md
+[previous]: ./README.md
+
 [fork-repo]: https://docs.github.com/en/get-started/quickstart/fork-a-repo
-[template-repo]: https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-template-repository
 [repo-root]: /
-[walkthrough-previous]: README.md
-[walkthrough-next]: 1-code-scanning.md
+[template-repo]: https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-template-repository

content/1-code-scanning.md

@@ -1,6 +1,6 @@
 # Securing the development pipeline
 
-| [← Workshop setup][walkthrough-previous] | [Next: Project management with GitHub Issues →][walkthrough-next] |
+| [← Workshop setup][previous] | [Next: Project management with GitHub Issues →][next] |
 |:-----------------------------------|------------------------------------------:|
 
 Ensuring code security is imperative in today's environment. When we think about how we create code today, there's three main areas to focus on:
@@ -84,25 +84,26 @@ A background process starts, and will configure a workflow for analyzing your co
 
 ## Summary and next steps
 
-In this exercise, you enabled GitHub Advanced Security. You enabled Dependabot to check the libraries your project takes dependencies on, secret scanning to look for keys and tokens, and code scanning to examine your source code. These tools help ensure your application is secure. Next it's time to [file an issue][walkthrough-next] to add feature requests.
+In this exercise, you enabled GitHub Advanced Security. You enabled Dependabot to check the libraries your project takes dependencies on, secret scanning to look for keys and tokens, and code scanning to examine your source code. These tools help ensure your application is secure. Next it's time to [file an issue][next] to add feature requests.
 
 ### Additional resources
 
 - [About GitHub Advanced Security][advanced-security-docs]
 - [GitHub Skills: Secure your repository's supply chain][skills-supply-chain]
 - [GitHub Skills: Secure code game][skills-secure-code]
 
-| [← Workshop setup][walkthrough-previous] | [Next: Project management with GitHub Issues →][walkthrough-next] |
+| [← Workshop setup][previous] | [Next: Project management with GitHub Issues →][next] |
 |:-----------------------------------|------------------------------------------:|
 
-[advanced-security]: https://github.com/features/security
-[advanced-security-docs]: https://docs.github.com/en/get-started/learning-about-github/about-github-advanced-security
+[next]: ./2-issues.md
+[previous]: ./0-setup.md
+
 [about-code-scanning]: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
 [about-prs]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
+[advanced-security]: https://github.com/features/security
+[advanced-security-docs]: https://docs.github.com/en/get-started/learning-about-github/about-github-advanced-security
 [dependabot-quickstart]: https://docs.github.com/en/code-security/getting-started/dependabot-quickstart-guide
 [github-actions]: https://github.com/features/actions
-[supported-secrets]: https://docs.github.com/en/code-security/secret-scanning/secret-scanning-patterns#supported-secrets
-[skills-supply-chain]: https://github.com/skills/secure-repository-supply-chain
 [skills-secure-code]: https://github.com/skills/secure-code-game
-[walkthrough-previous]: 0-setup.md
-[walkthrough-next]: 2-issues.md
+[skills-supply-chain]: https://github.com/skills/secure-repository-supply-chain
+[supported-secrets]: https://docs.github.com/en/code-security/secret-scanning/secret-scanning-patterns#supported-secrets

content/2-issues.md

@@ -1,6 +1,6 @@
 # Project management with GitHub Issues
 
-| [← Securing the development pipeline][walkthrough-previous] | [Next: Cloud-based development with GitHub Codespaces →][walkthrough-next] |
+| [← Securing the development pipeline][previous] | [Next: Cloud-based development with GitHub Codespaces →][next] |
 |:-----------------------------------|------------------------------------------:|
 
 "URL or it didn't happen" is a common mantra at GitHub, which is used to highlight the importance of documenting the development process. Feature requests should have a history: who made the request, what was the rationale, who was involved in the process, what decisions were made, why were they made, was the feature implemented, how was it implemented... All of this information helps provide context to both drive future decisions and avoid repeating old mistakes.
@@ -55,23 +55,24 @@ You've now defined all the issues for the workshop! You'll use these issues to h
 
 ## Summary and next steps
 
-GitHub Issues are the core to project management on GitHub. Their flexibility allows your organization to determine the best course of action to support your development lifecycle's methodology. With your issues created, it's time to turn your attention to the first big change to the project, [defining a codespace][walkthrough-next].
+GitHub Issues are the core to project management on GitHub. Their flexibility allows your organization to determine the best course of action to support your development lifecycle's methodology. With your issues created, it's time to turn your attention to the first big change to the project, [defining a codespace][next].
 
 ## Resources
 
 - [GitHub Issues][issues-docs]
 - [Communicate using markdown][skills-markdown]
 - [GitHub Projects][projects-docs]
 
-| [← Securing the development pipeline][walkthrough-previous] | [Next: Cloud-based development with GitHub Codespaces →][walkthrough-next] |
+| [← Securing the development pipeline][previous] | [Next: Cloud-based development with GitHub Codespaces →][next] |
 |:-----------------------------------|------------------------------------------:|
 
-[discussions]: https://github.com/features/discussions
-[wikis]: https://docs.github.com/en/communities/documenting-your-project-with-wikis/about-wikis
+[next]: ./3-codespaces.md
+[previous]: ./1-code-scanning.md
+
 [about-prs]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
+[discussions]: https://github.com/features/discussions
 [issues]: https://github.com/features/issues
 [issues-docs]: https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues
 [projects-docs]: https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects
 [skills-markdown]: https://github.com/skills/communicate-using-markdown
-[walkthrough-next]: 3-codespaces.md
-[walkthrough-previous]: 1-code-scanning.md
+[wikis]: https://docs.github.com/en/communities/documenting-your-project-with-wikis/about-wikis

content/3-codespaces.md

@@ -1,6 +1,6 @@
 # Cloud-based development with GitHub Codespaces
 
-| [← Project management with GitHub Issues][walkthrough-previous] | [Next: Continuous integration and testing →][walkthrough-next] |
+| [← Project management with GitHub Issues][previous] | [Next: Continuous integration and testing →][next] |
 |:-----------------------------------|------------------------------------------:|
 
 One of the biggest challenges organizations face is onboarding new developers to projects. There are libraries to install, services to configure, version issues, obscure error messages... It can literally take days to get everything running before a developer is able to write their first line of code.
@@ -129,7 +129,7 @@ Whenever someone uses the codespace you defined they'll have an environment with
 
 ## Interacting with the repository
 
-Custom containers for GitHub Codespaces become part of the source code for the repository. Thus they are maintained through standard source control, and will follow the repository as it's forked in the future. This allows this definition to be shared across all developers contributing to the project. Let's upload our new configuration, closing the [issue you created][walkthrough-previous] for defining a development environment.
+Custom containers for GitHub Codespaces become part of the source code for the repository. Thus they are maintained through standard source control, and will follow the repository as it's forked in the future. This allows this definition to be shared across all developers contributing to the project. Let's upload our new configuration, closing the [issue you created][previous] for defining a development environment.
 
 > [!IMPORTANT]
 > For purposes of this exercise we are pushing code updates directly to `main`, our default branch. Normally you would follow the [GitHub flow][github-flow], which we will do in a [later exercise][github-flow-exercise].
@@ -165,7 +165,7 @@ Custom containers for GitHub Codespaces become part of the source code for the r
 
 ## Summary and next steps
 
-Congratulations! You have now defined a custom development environment including all services and extensions. This eliminates the initial setup hurdle normally required when contributing to a project. Let's use this codespace to [implement testing and continuous integration][walkthrough-next] for the project.
+Congratulations! You have now defined a custom development environment including all services and extensions. This eliminates the initial setup hurdle normally required when contributing to a project. Let's use this codespace to [implement testing and continuous integration][next] for the project.
 
 ## Resources
 
@@ -174,23 +174,24 @@ Congratulations! You have now defined a custom development environment including
 - [Defining dev containers][dev-containers-docs]
 - [GitHub Skills: Code with Codespaces][skills-codespaces]
 
-| [← Project management with GitHub Issues][walkthrough-previous] | [Next: Continuous integration and testing →][walkthrough-next] |
+| [← Project management with GitHub Issues][previous] | [Next: Continuous integration and testing →][next] |
 |:-----------------------------------|------------------------------------------:|
 
+[next]: ./4-continuous-integration.md
+[previous]: ./2-issues.md
+[github-flow-exercise]: ./6-github-flow.md
+
+[codespace-prebuild]: https://docs.github.com/en/codespaces/prebuilding-your-codespaces
 [codespaces]: https://github.com/features/codespaces
+[codespaces-docs]: https://docs.github.com/en/codespaces/overview
 [codespaces-forward-ports]: https://docs.github.com/en/codespaces/developing-in-a-codespace/forwarding-ports-in-your-codespace
 [copilot-extension]: https://marketplace.visualstudio.com/items?itemName=GitHub.copilot
-[codespaces-docs]: https://docs.github.com/en/codespaces/overview
-[codespace-prebuild]: https://docs.github.com/en/codespaces/prebuilding-your-codespaces
 [dev-containers-docs]: https://docs.github.com/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers
 [github-flow]: https://docs.github.com/en/get-started/quickstart/github-flow
-[github-flow-exercise]: ./7-github-flow.md
 [github-universal-container]: https://docs.github.com/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers#using-the-default-dev-container-configuration
 [github-universal-container-definition]: https://github.com/devcontainers/images/blob/main/src/universal/.devcontainer/Dockerfile
 [IDE]: https://en.wikipedia.org/wiki/Integrated_development_environment
 [skills-codespaces]: https://github.com/skills/code-with-codespaces
 [vscode-codespaces]: https://docs.github.com/en/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code
 [vscode-extensions]: https://code.visualstudio.com/docs/editor/extension-marketplace
 [vscode-post-start-command]: https://code.visualstudio.com/remote/advancedcontainers/start-processes
-[walkthrough-previous]: 2-issues.md
-[walkthrough-next]: 4-testing.md

content/4-continuous-integration.md

@@ -1,6 +1,6 @@
 # Continuous integration and testing
 
-| [← Cloud-based development with GitHub Codespaces][walkthrough-previous] | [Next: Helping GitHub Copilot understand context →][walkthrough-next] |
+| [← Cloud-based development with GitHub Codespaces][previous] | [Next: Coding with GitHub Copilot →][next] |
 |:-----------------------------------|------------------------------------------:|
 
 Chances are you've heard the abbreviation CI/CD, which stands for continuous integration and continuous delivery (or sometimes continuous deployment). CI is centered on incorporating new code into the existing codebase, and typically includes running tests and performing builds. CD focuses on the next logical step, taking the now validated code and generating the necessary outputs to be pushed to the cloud or other destinations. This is probably the most focused upon component of DevOps.
@@ -141,7 +141,7 @@ You've now seen a workflow, and explore the details of a run!
 
 ## Summary and next steps
 
-Congratulations! You've implemented automated testing, a standard part of continuous integration, which is critical to successful DevOps. Automating these processes ensures consistency and reduces the workload required for developers and administrators. You have created a workflow to run tests on any new code for your codebase. Let's explore [context with GitHub Copilot chat][walkthrough-next].
+Congratulations! You've implemented automated testing, a standard part of continuous integration, which is critical to successful DevOps. Automating these processes ensures consistency and reduces the workload required for developers and administrators. You have created a workflow to run tests on any new code for your codebase. Let's explore [coding with GitHub Copilot][next].
 
 ### Resources
 
@@ -150,19 +150,20 @@ Congratulations! You've implemented automated testing, a standard part of contin
 - [About continuous integration][about-ci]
 - [GitHub Skills: Test with Actions][skills-test-actions]
 
-| [← Cloud-based development with GitHub Codespaces][walkthrough-previous] | [Next: Helping GitHub Copilot understand context →][walkthrough-next] |
+| [← Cloud-based development with GitHub Codespaces][previous] | [Next: Coding with GitHub Copilot →][next] |
 |:-----------------------------------|------------------------------------------:|
 
+[next]: ./5-code.md
+[previous]: ./3-codespaces.md
+[github-flow-exercise]: ./6-github-flow.md
+[issues-exercise]: ./2-issues.md
+
 [about-ci]: https://docs.github.com/en/actions/automating-builds-and-tests/about-continuous-integration
 [about-prs]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
 [actions-marketplace]: https://github.com/marketplace?type=actions
-[workflow-triggers]: https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows
 [copilot]: https://gh.io/copilot
 [copilot-slash-commands]: https://docs.github.com/en/copilot/using-github-copilot/copilot-chat/github-copilot-chat-cheat-sheet
 [github-actions]: https://github.com/features/actions
 [github-flow]: https://docs.github.com/en/get-started/quickstart/github-flow
-[github-flow-exercise]: ./7-github-flow.md
-[issues-exercise]: ./2-issues.md
 [skills-test-actions]: https://github.com/skills/test-with-actions
-[walkthrough-previous]: 3-codespaces.md
-[walkthrough-next]: 5-context.md
+[workflow-triggers]: https://docs.github.com/en/actions/reference/events-that-trigger-workflows