You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/pipelines/pipelines.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,7 +148,7 @@ Unlike other CI options, the Git repository that contains the pipeline can be co
148
148
149
149
**Use branch from Git trigger**
150
150
151
-
The**Use branch from Git trigger** option is very important, as it defines the branch in the Git repo the pipeline is loaded from. In most cases, you want to keep this enabled as it loads the pipeline from the same branch that triggered the build.
151
+
The**Use branch from Git trigger** option is very important, as it defines the branch in the Git repofrom whichthe pipeline is loaded. In most cases, you want to keep this enabled as it loads the pipeline from the same branch that triggered the build.
152
152
153
153
For example, if you open a new pull request for a branch named`feature-x`, that has changes both in source code and in the pipeline definition itself, ideally you would want the pipeline responsible for the build to be the same one that contains the new changes in the`feature-x` branch.
154
154
@@ -174,11 +174,11 @@ max-width="70%"
174
174
You can then copy and paste the URL to a raw Codefresh YAML file. This will allow you to load a Codefresh YAML from any URL.