remove all uses of include tool-switcher (part 1) (#24220)

* remove all uses of `include tool-switcher`

* two more files

content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md

@@ -31,8 +31,6 @@ You can also disable and enable a workflow using the REST API. For more informat
 
 ## Disabling a workflow
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -62,8 +60,6 @@ gh workflow disable <em>workflow</em>
 
 ## Enabling a workflow
 
-{% include tool-switcher %}
-
 {% webui %}
 
 You can re-enable a workflow that was previously disabled.

content/actions/managing-workflow-runs/downloading-workflow-artifacts.md

@@ -16,8 +16,6 @@ By default, {% data variables.product.product_name %} stores build logs and arti
 
 {% data reusables.repositories.permissions-statement-read %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}

content/actions/managing-workflow-runs/manually-running-a-workflow.md

@@ -20,8 +20,6 @@ To run a workflow manually, the workflow must be configured to run on the `workf
 
 ## Running a workflow
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}

content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md

@@ -19,8 +19,6 @@ versions:
 
 Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow for up to 30 days after the initial run.
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}

content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md

@@ -16,8 +16,6 @@ shortTitle: View workflow run history
 
 {% data reusables.repositories.permissions-statement-read %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}

content/actions/security-guides/encrypted-secrets.md

@@ -79,8 +79,6 @@ When generating credentials, we recommend that you grant the minimum permissions
 
 {% data reusables.github-actions.permissions-statement-secrets-repository %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -121,8 +119,6 @@ To list all secrets for the repository, use the `gh secret list` subcommand.
 
 {% data reusables.github-actions.permissions-statement-secrets-environment %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -160,8 +156,6 @@ When creating a secret in an organization, you can use a policy to limit which r
 
 {% data reusables.github-actions.permissions-statement-secrets-organization %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.organizations.navigate-to-org %}

content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md

@@ -24,7 +24,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% mac %}
 
-{% include tool-switcher %}
 {% webui %}
 
 1. Copy the SSH public key to your clipboard.
@@ -59,8 +58,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% windows %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 1. Copy the SSH public key to your clipboard.
@@ -96,7 +93,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% linux %}
 
-{% include tool-switcher %}
 {% webui %}
 
 1. Copy the SSH public key to your clipboard.

content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md

@@ -18,8 +18,6 @@ A codespace will stop running after a period of inactivity. You can specify the
 
 {% endwarning %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 ## Setting your default timeout

content/codespaces/developing-in-codespaces/creating-a-codespace.md

@@ -67,8 +67,6 @@ If you would like to create a codespace for a repository owned by your personal
 
 ## Creating a codespace
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}

content/codespaces/developing-in-codespaces/deleting-a-codespace.md

@@ -26,7 +26,6 @@ shortTitle: Delete a codespace
 
 {% endnote %}
 
-{% include tool-switcher %}
 
 {% webui %}
 

content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md

@@ -29,8 +29,6 @@ You can also forward a port manually, label forwarded ports, share forwarded por
 
 You can manually forward a port that wasn't forwarded automatically.
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -93,8 +91,6 @@ To see details of forwarded ports enter `gh codespace ports` and then choose a c
 
 If you want to share a forwarded port with others, you can either make the port private to your organization or make the port public. After you make a port private to your organization, anyone in the organization with the port's URL can view the running application. After you make a port public, anyone who knows the URL and port number can view the running application without needing to authenticate.
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}

content/codespaces/troubleshooting/codespaces-logs.md

@@ -23,8 +23,6 @@ Information on {% data variables.product.prodname_codespaces %} is output to thr
 
 These logs contain detailed information about the codespace, the container, the session, and the {% data variables.product.prodname_vscode %} environment. They are useful for diagnosing connection issues and other unexpected behavior. For example, the codespace freezes but the "Reload Windows" option unfreezes it for a few minutes, or you are randomly disconnected from the codespace but able to reconnect immediately.
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 1. If you are using {% data variables.product.prodname_codespaces %} in the browser, ensure that you are connected to the codespace you want to debug.
@@ -51,7 +49,6 @@ Currently you can't use {% data variables.product.prodname_cli %} to access thes
 
 These logs contain information about the container, dev container, and their configuration. They are useful for debugging configuration and setup problems.
 
-{% include tool-switcher %}
 
 {% webui %}
 

content/get-started/quickstart/contributing-to-projects.md

@@ -35,7 +35,6 @@ You've successfully forked the Spoon-Knife repository, but so far, it only exist
 
 You can clone your fork with the command line, {% data variables.product.prodname_cli %}, or {% data variables.product.prodname_desktop %}.
 
-{% include tool-switcher %}
 {% webui %}
 
 1. On {% data variables.product.product_name %}, navigate to **your fork** of the Spoon-Knife repository.
@@ -87,7 +86,6 @@ Go ahead and make a few changes to the project using your favorite text editor,
 
 When you're ready to submit your changes, stage and commit your changes. `git add .` tells Git that you want to include all of your changes in the next commit. `git commit` takes a snapshot of those changes.
 
-{% include tool-switcher %}
 {% webui %}
 
 ```shell
@@ -116,7 +114,6 @@ When you stage and commit files, you essentially tell Git, "Okay, take a snapsho
 
 Right now, your changes only exist locally. When you're ready to push your changes up to {% data variables.product.product_name %}, push your changes to the remote.
 
-{% include tool-switcher %}
 {% webui %}
 
 ```shell

content/get-started/quickstart/create-a-repo.md

@@ -39,8 +39,6 @@ You can store a variety of projects in {% data variables.product.product_name %}
 
 {% endif %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.create_new %}
@@ -69,8 +67,6 @@ Congratulations! You've successfully created your first repository, and initiali
 
 ## Commit your first change
 
-{% include tool-switcher %}
-
 {% webui %}
 
 A *[commit](/articles/github-glossary#commit)* is like a snapshot of all the files in your project at a particular point in time.