Skip to content

Commit b198076

Browse files
committed
Shorter sentences
1 parent 1ccbb81 commit b198076

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/azure-devops.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -206,7 +206,7 @@ The `azure-release-pipeline.yaml` is the main pipeline, and is the one that will
206206

207207
You can add your Build and Test stage between the `cloudSyncStage` and `cloudPrepareArtifact` stages. Keep in mind that you do not need to retain the dotnet build artifact for upload later. The `cloudPrepareArtifact` job will take care of packaging all your source code and upload to Umbraco Cloud.
208208

209-
If you add Build and Test stages after `cloudSyncStage` make sure that you checkout the updated code in case there were applied a git patch to your repository.
209+
Make sure that you checkout the potentially updated code if you add Build and Test steps.
210210

211211
### Cloud-sync
212212

umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/github-actions.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -235,7 +235,8 @@ The `main.yml` is the main pipeline, and is the one that will be triggered on a
235235

236236
You can add your Build and Test jobs between the `cloud-sync` and `cloud-artifact` jobs. Keep in mind that you do not need to retain the dotnet build artifact for upload later. The `cloud-artifact` job will take care of packaging all your source code and upload to Umbraco Cloud.
237237

238-
If you add Build and Test stages after `cloud-sync` make sure that you checkout the updated code in case there were applied a git patch to your repository.
238+
Make sure that you checkout the potentially updated code if you add Build and Test steps.
239+
239240
### Cloud-sync
240241

241242
The `cloud-sync.yml` shows how you can sync your GitHub repository with the targeted environment of your Cloud project. In this sample, it accepts any change from the API and applies and commits it back to the branch which triggered the pipeline. However the commit does not trigger the pipeline again.

0 commit comments

Comments
 (0)