@@ -134,7 +134,8 @@ where items have the following meaning:
134134 bots from this PR would be used instead of master.
135135- owner/project: Name of github project (e.g. 'cockpit-project/cockpit'). This part can
136136 be omitted when testing in the same project and no 'ref' is needed.
137- - ref: Reference in the project (usually branch) (e.g. 'rhel-8.2'). Default is 'master'.
137+ - ref: Reference in the project (usually branch) (e.g. 'rhel-8.2'). Default is
138+ the project's primary branch.
138139
139140For example, context for scenario 'firefox' on 'fedora-testing' is:
140141
@@ -144,7 +145,7 @@ If we want to trigger it on 'cockpit-project/cockpit':
144145
145146 fedora-testing/firefox@cockpit-project/cockpit
146147
147- If we want to also not run it on master branch, but on 'rhel-8-0' branch:
148+ If we want to also not run it on the primary branch, but on 'rhel-8-0' branch:
148149
149150 fedora-testing/firefox@cockpit-project/cockpit/rhel-8-0
150151
@@ -202,7 +203,7 @@ any way you like.
202203
203204If you are certain about the changes to the images, it is probably a
204205good idea to make a dedicated pull request just for the images. That
205- pull request can then hopefully be merged to master faster. If
206+ pull request can then hopefully be merged faster. If
206207instead the images are created on the main feature pull request and
207208sit there for a long time, they might cause annoying merge conflicts.
208209
0 commit comments