Pull Requests

Buddybuild triggers a new build whenever a pull request is opened and when commits are added to an existing pull request. The commit’s status is updated in GitHub, Bitbucket or GitLab so that you can tell if the pull request is safe to merge.

Merge commit behavior

Rather than simply building each pull request commit, instead buddybuild builds the merge of that pull request commit and the tip of its base branch. In other words, we build the pull request merge commit so that you always know if your changes are safe to merge.

Similarly when you click on Build Now on an open pull request in buddybuild we build the merge commit of the latest pull request commit against the tip of its base branch.

Enabling pull requests


Looking for Pull Request in buddybuild?

Pull request features are available for GitHub, Bitbucket or GitLab apps if you have signed up with those services in buddybuild.

Visit your build settings and ensure that the Build pull requests setting is enabled.

The Default build configuration screen, with the Build pull requests option enabled

If Build pull requests is enabled then buddybuild builds the pull request merge commit when you open a pull request and whenever you push code to a pull request, instead of building the pull request commit.

Otherwise, if Build pushes is enabled then buddybuild builds your commit when you push code.

Optimizing your setup

For larger teams we recommend that you enable pull requests by default for all branches and build pushes for base branches only. This allows your team to have the latest pull request commit status and the latest commit status on your base branches (like develop and master), while reducing the noise of unstable feature branches.

This can be done by ensuring that Build pushes is disabled by default but enabled for each of your base branches (develop, master and release for example) in the Branch-specific configurations.

The Override build configuration area, with Build pushes option selected

Cross-repository pull requests

By default, cross-repository pull requests are disabled in buddybuild. This is a security feature. See Build secrets for details.

To enable this feature:

  1. Log in to the buddybuild dashboard.

  2. The App Settings button Click App Settings button in the top toolbar. The Default build configuration screen is displayed:

    The Default build configuration screen

  3. In the Build pull requests row, click the Configure link. The Configure cross-repository pull requests dialog is displayed:

    The Configure cross-repository pull requests dialog

  4. Click the toggle beside Build cross-repository pull requests to enable building of cross-repository pull requests.

  5. Either click the toggle beside Build all forked repositories to enable building of all forked repositories, or click the toggle beside any specific forked repositories listed.


Enabling cross-repository pull request builds means that you trust the forked repositories and their users. Trusting a forked repository increases your security risk. When you configure buddybuild to build pull requests, users with access to the forked repository can create a pull request that adds/changes a custom build step such that it can capture secrets, source code, etc., and can potentially be used to gain full access to your main repository.

results matching ""

    No results matching ""