# External contributions

When a pull request is coming from a non-Sourcegrapher, it won’t trigger a CI
build on Buildkite automatically because we want to review the code before it
runs on our CI infrastructure. Please review the PR to ensure it doesn’t make
any malicious changes to our build scripts.

## Triggering a build

There are two options to trigger a build.

## Option 1: On the command line

Pull the PR branch locally, and push it upstream:

```
git fetch origin pull/<PR-NUMBER>/head:<LOCAL-BRANCH-NAME-YOU-CHOOSE>
git push origin <LOCAL-BRANCH-NAME-YOU-CHOOSE>
```

If the PR changes, pull changes into the branch, and then push it upstream
again.

## Option 2: In the Buildkite web interface

1. Find the full length SHA of the latest commit, e.g. `ae724a83f8b6fc5628a4e8efcbb62975ed7b4c33` for #8234.
1. Find the branch name, e.g. `8160-http-warning` (trim `Akarshit:` prefix) for #8234.
1. Go to https://buildkite.com/sourcegraph/sourcegraph and click on **New Build** on the top-right menu.
1. Fill in message (could be anything, copy the pull request title is better), commit SHA and branch.
1. Click on **Create Build**, then the build status should be updated in the pull request checks.


<section class="h0Wrapper headingWrapper"><section class="h1Wrapper headingWrapper"><h1 id="external-contributions"><a class="anchor" aria-hidden tabindex="-1" href="#external-contributions"><span class="icon icon-link"></span></a>External contributions</h1>
<p>When a pull request is coming from a non-Sourcegrapher, it won’t trigger a CI
build on Buildkite automatically because we want to review the code before it
runs on our CI infrastructure. Please review the PR to ensure it doesn’t make
any malicious changes to our build scripts.</p>
<section class="h2Wrapper headingWrapper"><h2 id="triggering-a-build"><a class="anchor" aria-hidden tabindex="-1" href="#triggering-a-build"><span class="icon icon-link"></span></a>Triggering a build</h2>
<p>There are two options to trigger a build.</p>
</section><section class="h2Wrapper headingWrapper"><h2 id="option-1-on-the-command-line"><a class="anchor" aria-hidden tabindex="-1" href="#option-1-on-the-command-line"><span class="icon icon-link"></span></a>Option 1: On the command line</h2>
<p>Pull the PR branch locally, and push it upstream:</p>
<pre><code class="hljs language-php-template"><span class="xml">git fetch origin pull/<span class="hljs-tag">&#x3C;<span class="hljs-name">PR-NUMBER</span>></span>/head:<span class="hljs-tag">&#x3C;<span class="hljs-name">LOCAL-BRANCH-NAME-YOU-CHOOSE</span>></span>
git push origin <span class="hljs-tag">&#x3C;<span class="hljs-name">LOCAL-BRANCH-NAME-YOU-CHOOSE</span>></span>
</span></code></pre>
<p>If the PR changes, pull changes into the branch, and then push it upstream
again.</p>
</section><section class="h2Wrapper headingWrapper"><h2 id="option-2-in-the-buildkite-web-interface"><a class="anchor" aria-hidden tabindex="-1" href="#option-2-in-the-buildkite-web-interface"><span class="icon icon-link"></span></a>Option 2: In the Buildkite web interface</h2>
<ol>
<li>Find the full length SHA of the latest commit, e.g. <code>ae724a83f8b6fc5628a4e8efcbb62975ed7b4c33</code> for <a href="https://github.com/sourcegraph/sourcegraph/issues/8234">#8234</a>.</li>
<li>Find the branch name, e.g. <code>8160-http-warning</code> (trim <code>Akarshit:</code> prefix) for <a href="https://github.com/sourcegraph/sourcegraph/issues/8234">#8234</a>.</li>
<li>Go to <a href="https://buildkite.com/sourcegraph/sourcegraph">https://buildkite.com/sourcegraph/sourcegraph</a> and click on <strong>New Build</strong> on the top-right menu.</li>
<li>Fill in message (could be anything, copy the pull request title is better), commit SHA and branch.</li>
<li>Click on <strong>Create Build</strong>, then the build status should be updated in the pull request checks.</li>
</ol></section></section></section>