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/triggers/git-triggers.md
+39-29Lines changed: 39 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ max-width="50%"
69
69
|**Trigger Name**| Required. A freetext name for the Git trigger.|
70
70
|**Description**| Optional. A freetext description.|
71
71
|**Repository**| The repository in the Git provider account to track for the trigger event. You can select any repository, even one different from that used for the code checkout.|
72
-
|**Trigger By**| The event or events for which to trigger the pipeline. Trigger events vary according to the Git provider selected. <br>The Push Commit option, enabled by default, means that this pipeline will run for*any* commit as long as its source branch matches the naming scheme. This includes commits on pull requests. <br>The PR options mean that this pipeline will run only on the respective events that happen on aPull Request. You can select multiple options to further fine-tune the exact event. If you are interested in all events, select AnyPull Request event. <br><br>See: <br>[GitHub trigger events](#github-trigger-events)<br>[Azure DevOps trigger events](#azure-devops-trigger-events)<br>[Bitbucket trigger events](#bitbucket-trigger-events)<br>[GitLab trigger events](#gitlab-trigger-events)<br>[Gerrit trigger events](#gerrit-trigger-events)|
72
+
|**Trigger By**| The event or events for which to trigger the pipeline. Trigger events vary according to the Git provider selected. <br>The Push Commit option, enabled by default, means that this pipeline will run for*any* commit as long as its source branch matches the naming scheme. This includes commits on pull requests. <br>The PR options mean that this pipeline will run only on the respective events that happen on apull request. You can select multiple options to further fine-tune the exact event. If you are interested in all events, select Anypull request event. <br><br>See: <br>[GitHub trigger events](#github-trigger-events)<br>[Azure DevOps trigger events](#azure-devops-trigger-events)<br>[Bitbucket trigger events](#bitbucket-trigger-events)<br>[GitLab trigger events](#gitlab-trigger-events)<br>[Gerrit trigger events](#gerrit-trigger-events)|
73
73
74
74
75
75
@@ -80,23 +80,33 @@ For a description of the events, see [GitHub documentation](https://docs.github.
80
80
81
81
* Push commits
82
82
* Push tags
83
-
* Any Pull Request event
84
-
* Pull Request opened
85
-
* Pull Request closed
86
-
* Pull Request merged
87
-
* Pull Request closed (not merged)
88
-
* Pull Request reopened
89
-
* Pull Request edited
90
-
* Pull Request assigned
91
-
* Pull Request unassigned
92
-
* Pull Request review requested
93
-
* Pull Request review request removed
94
-
* Pull Request labeled
95
-
* Pull Request unlabeled
96
-
* Pull Request synchronized
97
-
* Pull Request comment added (restricted)
98
-
* Pull Request comment added
99
-
* Release
83
+
* Any pull request event
84
+
* Pull request opened
85
+
* Pull request closed
86
+
* Pull request merged
87
+
* Pull request closed (not merged)
88
+
* Pull request reopened
89
+
* Pull request edited
90
+
* Pull request assigned
91
+
* Pull request unassigned
92
+
* Pull request review requested
93
+
* Pull request review request removed
94
+
* Pull request labeled
95
+
* Pull request unlabeled
96
+
* Pull request synchronized
97
+
* Pull request comment added (restricted)
98
+
* Pull request comment added
99
+
* Pull request review approved
100
+
* Pull request review commented
101
+
* Pull request review changes requested
102
+
* Release published
103
+
* Release unpublished
104
+
* Release created
105
+
* Release edited
106
+
* Release deleted
107
+
* Release prereleased
108
+
* Release released
109
+
100
110
101
111
102
112
####Azure DevOps trigger events
@@ -117,7 +127,7 @@ For a description of the events and their payload, see [Bitbucket Cloud document
117
127
* Commit
118
128
* Push tags
119
129
* Push new branch
120
-
* AnyPull Request event
130
+
* Anypull request event
121
131
* Pull request created
122
132
* Pull request updated
123
133
* Pull request approved
@@ -137,7 +147,7 @@ For a description of the events and their payload, see [Bitbucket Server documen
137
147
* Push commits
138
148
* Push new branch
139
149
* Delete branch
140
-
* AnyPull request event
150
+
* Anypull request event
141
151
* Pull request created
142
152
* Pull request updated
143
153
* Pull request merged
@@ -157,12 +167,12 @@ For a description of the events and their payload, see [Bitbucket Server documen
157
167
For a description of the events, see[GitLab documentation](https://docs.gitlab.com/ee/user/project/integrations/webhook_events.html){:target="\_blank"}.
158
168
159
169
* Commit
160
-
* Any PullRequest event
161
-
* PullRequest opened
162
-
* PullRequest edited
163
-
* PullRequest closed
164
-
* PullRequest merged
165
-
* PullRequest push commit
170
+
* Any Pullrequest event
171
+
* Pullrequest opened
172
+
* Pullrequest edited
173
+
* Pullrequest closed
174
+
* Pullrequest merged
175
+
* Pullrequest push commit
166
176
167
177
168
178
####Gerrit trigger events
@@ -243,9 +253,9 @@ Remember to include the opening and closing parentheses when adding the strings.
243
253
*`[skip codefresh]`
244
254
*`[codefresh skip]`
245
255
246
-
###PullRequests from comments
256
+
###Pullrequests from comments
247
257
248
-
PullRequests from comments are supported for all Git providers, for both private and public repositories.
258
+
Pullrequests from comments are supported for all Git providers, for both private and public repositories.
249
259
There are two options:
250
260
* Pull request comment added (restricted)
251
261
This option triggers an event only when the PR comments are made by repository owners or collaborators.
@@ -330,7 +340,7 @@ caption="Triggering a public build from a comment"
330
340
max-width="50%"
331
341
%}
332
342
333
-
Once that is done, Codefresh will launch your pipeline against thePull Request. If you manage an open source project with Codefresh, remember to enable[public builds]({{site.baseurl}}/docs/pipelines/configuration/build-status/#public-build-logs) as well.
343
+
Once that is done, Codefresh will launch your pipeline against thepull request. If you manage an open source project with Codefresh, remember to enable[public builds]({{site.baseurl}}/docs/pipelines/configuration/build-status/#public-build-logs) as well.
334
344
335
345
When supporting building of pull requests from forks there are a few "gotchas" to look out for: