Skip to content

Commit 1103761

Browse files
resolve blocking issue 1
1 parent f7bc2e9 commit 1103761

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/sentinel/ci-cd.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ Select one of the following tabs depending on your connection type:
153153

154154
In the default configuration shown above for the `on` section, the wildcards (`**`) in the first line in the `paths` section indicate that the entire branch is in the path for the deployment triggers.
155155

156-
This default configuration means that a deployment workflow is triggered any time that content is pushed to any part of the branch.
156+
This default configuration means that a deployment workflow is triggered anytime that content is pushed to any part of the branch.
157157

158158
Later on in the file, the `jobs` section includes the following default configuration: `directory: '${{ github.workspace }}'`. This line indicates that the entire GitHub branch is in the path for the content deployment, without filtering for any folder paths.
159159

@@ -203,7 +203,7 @@ For more information, see the [GitHub documentation](https://docs.github.com/en/
203203
- main
204204
```
205205

206-
This default configuration means that a deployment pipeline is triggered any time that content is pushed to any part of the `main` branch.
206+
This default configuration means that a deployment pipeline is triggered anytime that content is pushed to any part of the `main` branch.
207207

208208
To deploy content from a specific folder path only, add the folder name to the `include` section, for the trigger, and the `steps` section, for the deployment path, below as needed.
209209

0 commit comments

Comments
 (0)