Skip to content

Commit 9d9f9fe

Browse files
Merge pull request #2954 from itecompro/fix-github-brand-name
docs(devtools/ci-cd): change 'Github' to 'GitHub'
2 parents 87ccf9b + d3a2d8f commit 9d9f9fe

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/devtools/ci-cd.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -83,9 +83,9 @@ See screenshot below:
8383

8484
The ability to go back in time lets you investigate and troubleshoot the issue by comparing the current graph with the previous one. Depending on how you set things up, every pull request (or even every commit) will have a corresponding snapshot in the registry, so you can easily go back in time and see what changed. Think of Devtools as a Git but with an understanding of how Nest constructs your application graph, and with the ability to **visualize** it.
8585

86-
#### Integrations: Github Actions
86+
#### Integrations: GitHub Actions
8787

88-
First let's start from creating a new Github workflow in the `.github/workflows` directory in our project and call it, for example, `publish-graph.yml`. Inside this file, let's use the following definition:
88+
First let's start from creating a new GitHub workflow in the `.github/workflows` directory in our project and call it, for example, `publish-graph.yml`. Inside this file, let's use the following definition:
8989

9090
```yaml
9191
name: Devtools
@@ -130,7 +130,7 @@ jobs:
130130
TARGET_SHA: {{ '${{' }} github.event.pull_request.base.sha {{ '}}' }}
131131
```
132132
133-
Ideally, `DEVTOOLS_API_KEY` environment variable should be retrieved from Github Secrets, read more [here](https://docs.github.com/en/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository) .
133+
Ideally, `DEVTOOLS_API_KEY` environment variable should be retrieved from GitHub Secrets, read more [here](https://docs.github.com/en/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository) .
134134

135135
This workflow will run per each pull request that's targeting the `master` branch OR in case there's a direct commit to the `master` branch. Feel free to align this configuration to whatever your project needs. What's essential here is that we provide necessary environment varaiables for our `GraphPublisher` class (to run).
136136

@@ -150,7 +150,7 @@ const publishOptions = {
150150
};
151151
```
152152

153-
For the best developer experience, make sure to integrate the **Github application** for your project by clicking on the "Integrate Github app" button (see screenshot below). Note - this isn't required.
153+
For the best developer experience, make sure to integrate the **GitHub application** for your project by clicking on the "Integrate GitHub app" button (see screenshot below). Note - this isn't required.
154154

155155
<figure><img src="/assets/devtools/integrate-github-app.png" /></figure>
156156

0 commit comments

Comments
 (0)