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: bert_e/docs/USER_DOC.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -119,6 +119,7 @@ __Bert-E__.
119
119
| bypass_peer_approval | Bypass the pull request peer's approval | yes | no
120
120
| bypass_leader_approval | Bypass the pull request leader's approval | yes | no
121
121
| create_pull_requests | Let __Bert-E__ create pull requests corresponding to integration branches | no | no
122
+
| create_integration_branches | Request __Bert-E__ to create integration branches and move forward with the gitwaterflow | no | no
122
123
| no_octopus | Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead | yes | no
123
124
| unanimity | Change review acceptance criteria from `one reviewer at least` to `all reviewers` (**this feature is not supported on GitHub**) | no | no
124
125
| wait | Instruct __Bert-E__ not to run until further notice | no | no
@@ -170,6 +171,19 @@ target development branch. This code is then tested in the build pipeline,
170
171
before any merge can happen. There are as many integration branches as there
171
172
are target branches.
172
173
174
+
The integration branches are mandatory in the GitWaterFlow process,
175
+
and by default they are automatically created when a pull request is
176
+
opened.
177
+
This behaviour can be changed with the `always_create_integration_branches`
178
+
parameter in the bot settings:
179
+
180
+
**true* (default): integration branches are created automatically when a
181
+
pull request is opened.
182
+
**false*: users will be required to explicitly request the creation
183
+
of integration branches by adding a `/create_integration_branches`
184
+
comment in their pull request (or it will be set for them during
185
+
other operations, like `approve` or `create_pull_requests`).
186
+
173
187
On the Git project, the name of the integration branches follow the format:
0 commit comments