fix incorrect code languages
This commit is contained in:
@@ -238,7 +238,7 @@ steps:
|
|||||||
|
|
||||||
The example above creates an _.npmrc_ file with the following contents:
|
The example above creates an _.npmrc_ file with the following contents:
|
||||||
|
|
||||||
```ini
|
```shell
|
||||||
//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
|
//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
|
||||||
@octocat:registry=https://registry.npmjs.org/
|
@octocat:registry=https://registry.npmjs.org/
|
||||||
always-auth=true
|
always-auth=true
|
||||||
|
|||||||
@@ -45,7 +45,7 @@ If setting environment variables is not practical, you can set the proxy configu
|
|||||||
|
|
||||||
### Example `.env` proxy configuration
|
### Example `.env` proxy configuration
|
||||||
|
|
||||||
```ini
|
```shell
|
||||||
https_proxy=http://proxy.local:8080
|
https_proxy=http://proxy.local:8080
|
||||||
no_proxy=example.com,myserver.local:443
|
no_proxy=example.com,myserver.local:443
|
||||||
```
|
```
|
||||||
|
|||||||
@@ -83,7 +83,7 @@ jobs:
|
|||||||
|
|
||||||
In the example above, the `setup-node` action creates an `.npmrc` file on the runner with the following contents:
|
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.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
|
||||||
registry=https://registry.npmjs.org/
|
registry=https://registry.npmjs.org/
|
||||||
always-auth=true
|
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.
|
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}
|
//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
|
||||||
@octocat:registry=https://npm.pkg.github.com
|
@octocat:registry=https://npm.pkg.github.com
|
||||||
always-auth=true
|
always-auth=true
|
||||||
|
|||||||
@@ -127,7 +127,7 @@ If any of these services are at or near 100% CPU utilization, or the memory is n
|
|||||||
- `actions.hcl.ctmpl`
|
- `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:
|
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 {
|
resources {
|
||||||
cpu = 512
|
cpu = 512
|
||||||
memory = 2048
|
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:
|
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 {
|
resources {
|
||||||
cpu = 1024
|
cpu = 1024
|
||||||
memory = 4096
|
memory = 4096
|
||||||
|
|||||||
@@ -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.
|
For example, the global `.gitconfig` for the CI machine would include these lines.
|
||||||
|
|
||||||
```gitconfig
|
```text
|
||||||
[url "https://europe-ci.github.example.com/"]
|
[url "https://europe-ci.github.example.com/"]
|
||||||
insteadOf = https://github.example.com/
|
insteadOf = https://github.example.com/
|
||||||
```
|
```
|
||||||
|
|||||||
@@ -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`.
|
Specify the first cluster node you configured as the MySQL primary via `mysql-server` and `mysql-master`.
|
||||||
|
|
||||||
```ini
|
```shell
|
||||||
[cluster]
|
[cluster]
|
||||||
mysql-master = ghes-database-node-1
|
mysql-master = ghes-database-node-1
|
||||||
redis-master = ghes-database-node-1
|
redis-master = ghes-database-node-1
|
||||||
|
|||||||
@@ -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. 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:
|
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
|
# .git-blame-ignore-revs
|
||||||
# Removed semi-colons from the entire codebase
|
# Removed semi-colons from the entire codebase
|
||||||
a8940f7fbddf7fad9d7d50014d4e8d46baf30592
|
a8940f7fbddf7fad9d7d50014d4e8d46baf30592
|
||||||
|
|||||||
Reference in New Issue
Block a user