Merge your first pull request

Protect the target branchCopy Anchor Link

Two rulesets on the target branch make every merge go through the queue: one that restricts the updates, with the App in its bypass list in the mode Exempt, and one that holds the rules of a pull request. Turn off "Require branches to be up to date before merging". Protect the target branch gives each click.

Check that your CI runs on the testsCopy Anchor Link

By default, each test of the queue opens a draft pull request: a workflow on pull_request runs on it without a change, if it does not skip draft pull requests. The test waits for the required checks of the rules of the branch. Run your CI on the tests of the queue covers GitHub Actions and the other CIs.

Submit a pull requestCopy Anchor Link

Choose a pull request of the default branch that is approved and whose checks pass, and comment:

/cihub merge

CIHub adds a 👍 reaction, then a comment that it keeps up to date, and the status CIHub Merge Queue (main):

The pull request merges when its test passes. If it waits, the comment says why: The life of a pull request in the queue.

Follow the queueCopy Anchor Link

The link Open in CIHub of the comment opens the pull request in the dashboard, with its queue. From a terminal, the command line shows the same:

cihub auth login --hostname cihub.example.com   # approve the code in the dashboard
cihub queue status

Install the command line first.

In a CI, set CIHUB_HOST and CIHUB_TOKEN, with an API token of the organization.