From c0a1de57f14d024f37ba9ccf269feba09fb42d56 Mon Sep 17 00:00:00 2001 From: Rachael Sewell Date: Mon, 25 Sep 2023 11:35:51 -0700 Subject: [PATCH] fix incorrect code languages --- .../building-and-testing-nodejs.md | 2 +- .../using-a-proxy-server-with-self-hosted-runners.md | 2 +- .../actions/publishing-packages/publishing-nodejs-packages.md | 4 ++-- .../troubleshooting-github-actions-for-your-enterprise.md | 4 ++-- .../caching-repositories/configuring-a-repository-cache.md | 2 +- .../configuring-clustering/initializing-the-cluster.md | 2 +- .../working-with-files/using-files/viewing-a-file.md | 2 +- 7 files changed, 9 insertions(+), 9 deletions(-) diff --git a/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index a474a1d7c6..6641e3ba85 100644 --- a/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -238,7 +238,7 @@ steps: The example above creates an _.npmrc_ file with the following contents: -```ini +```shell //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://registry.npmjs.org/ always-auth=true diff --git a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-a-proxy-server-with-self-hosted-runners.md b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-a-proxy-server-with-self-hosted-runners.md index 49635163b9..9c7f103aa6 100644 --- a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -45,7 +45,7 @@ If setting environment variables is not practical, you can set the proxy configu ### Example `.env` proxy configuration -```ini +```shell https_proxy=http://proxy.local:8080 no_proxy=example.com,myserver.local:443 ``` diff --git a/content/actions/publishing-packages/publishing-nodejs-packages.md b/content/actions/publishing-packages/publishing-nodejs-packages.md index d9fa4c8115..19fe4b20c9 100644 --- a/content/actions/publishing-packages/publishing-nodejs-packages.md +++ b/content/actions/publishing-packages/publishing-nodejs-packages.md @@ -83,7 +83,7 @@ jobs: In the example above, the `setup-node` action creates an `.npmrc` file on the runner with the following contents: -```ini +```shell //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} registry=https://registry.npmjs.org/ always-auth=true @@ -148,7 +148,7 @@ jobs: The `setup-node` action creates an `.npmrc` file on the runner. When you use the `scope` input to the `setup-node` action, the `.npmrc` file includes the scope prefix. By default, the `setup-node` action sets the scope in the `.npmrc` file to the account that contains that workflow file. -```ini +```shell //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN} @octocat:registry=https://npm.pkg.github.com always-auth=true diff --git a/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md index f9d3938a64..1ee4b9696f 100644 --- a/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md +++ b/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md @@ -127,7 +127,7 @@ If any of these services are at or near 100% CPU utilization, or the memory is n - `actions.hcl.ctmpl` 1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following: - ```terraform + ```text resources { cpu = 512 memory = 2048 @@ -141,7 +141,7 @@ If any of these services are at or near 100% CPU utilization, or the memory is n For example, to increase the resource limits in the above example to 1 GHz for the CPU and 4 GB of memory, change it to: - ```terraform + ```text resources { cpu = 1024 memory = 4096 diff --git a/content/admin/monitoring-managing-and-updating-your-instance/caching-repositories/configuring-a-repository-cache.md b/content/admin/monitoring-managing-and-updating-your-instance/caching-repositories/configuring-a-repository-cache.md index 48f2aa45d1..d601a63d32 100644 --- a/content/admin/monitoring-managing-and-updating-your-instance/caching-repositories/configuring-a-repository-cache.md +++ b/content/admin/monitoring-managing-and-updating-your-instance/caching-repositories/configuring-a-repository-cache.md @@ -24,7 +24,7 @@ To have your CI machines fetch from the repository cache instead of the primary For example, the global `.gitconfig` for the CI machine would include these lines. -```gitconfig +```text [url "https://europe-ci.github.example.com/"] insteadOf = https://github.example.com/ ``` diff --git a/content/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/initializing-the-cluster.md b/content/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/initializing-the-cluster.md index d249306246..b2aa3fff55 100644 --- a/content/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/initializing-the-cluster.md +++ b/content/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/initializing-the-cluster.md @@ -63,7 +63,7 @@ The names of the nodes can be any valid hostname you choose. The names are set a Specify the first cluster node you configured as the MySQL primary via `mysql-server` and `mysql-master`. -```ini +```shell [cluster] mysql-master = ghes-database-node-1 redis-master = ghes-database-node-1 diff --git a/content/repositories/working-with-files/using-files/viewing-a-file.md b/content/repositories/working-with-files/using-files/viewing-a-file.md index b3f8fde37f..90d22e15b5 100644 --- a/content/repositories/working-with-files/using-files/viewing-a-file.md +++ b/content/repositories/working-with-files/using-files/viewing-a-file.md @@ -71,7 +71,7 @@ All revisions specified in the `.git-blame-ignore-revs` file, which must be in t 1. In the root directory of your repository, create a file named `.git-blame-ignore-revs`. 1. Add the commit hashes you want to exclude from the blame view to that file. We recommend the file to be structured as follows, including comments: - ```ini + ```shell # .git-blame-ignore-revs # Removed semi-colons from the entire codebase a8940f7fbddf7fad9d7d50014d4e8d46baf30592