Skip to content

Commit 1b5440b

Browse files
authored
merge queues (#3235)
1 parent 4aa4656 commit 1b5440b

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

content/yaml-running-builds/starting-builds-automatically.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,18 @@ For repositories added via SSH or HTTP/HTTPS, or if you are configuring your bui
2121

2222
In the `events:` section, specify which events in the repository trigger builds.
2323
- **push** - a build will be started every time you commit code to any of the tracked branches.
24+
25+
GitHub Merge Queue as a feature helps manage and automate the process of merging multiple pull requests (PRs) into a branch. Merge Queue allows to automate and serialize merges, making sure that every pull request is tested not in isolation, but as it will be after it’s merged. More information can be found [here](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue).
26+
27+
To configure it with Codemagic workflows, a branch name prefixed with *gh-readonly-queue/{base_branch}* needs to be added in **codemagic.yaml** as explained [here](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue#triggering-merge-group-checks-with-third-party-ci-providers)
28+
{{< highlight yaml "style=paraiso-dark">}}
29+
triggering:
30+
events:
31+
- push
32+
branch_patterns:
33+
- pattern: 'gh-readonly-queue/main/*'
34+
{{< /highlight >}}
35+
2436
- **pull_request** - a build will be started when a pull request is opened or updated to verify the resulting merge commit.
2537

2638
For triggering pull requests, you can specify whether each branch pattern matches the **source** or the **target** branch of the pull request.

0 commit comments

Comments
 (0)