Hosts the code for the Trunk Merge Github Action. To get beta access to the Merge Graph, contact us on Slack.
Trunk’s MergeGraph keeps your main branch green by ensuring that tests pass prior to merging your main branch. The MergeGraph, unlike traditional MergeQueues, increases throughput by only testing dependent PRs; no more waiting for your backend changes to test before landing your docs!
After creating a MergeGraph at app.trunk.io, simply comment /trunk merge on your
PRs to submit it to the graph. Once the graph has passed the prerequisites to be admitted into the
graph (impacted targets have been uploaded, Github deems the PR mergeable), the Trunk Service will
en-graph the PR, constructing a test branch between the PR and all of its ancestors. On successful
completion of tests, Trunk merges the PR, keeping your main branch green 😎.
name: Upload Impacted Targets
on: pull_request
jobs:
compute_impacted_targets:
name: Compute Impacted Targets
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Compute Impacted Targets
uses: trunk-io/merge-action@v1
with:
### Use your repositories API token to authenticate impacted targets uploads.
trunk-token: ${{ secrets.TRUNK_REPO_API_TOKEN }}pnpm install
pnpm test
An impacted target is a unit that is affected by a particular PR. For example, a change at
src/backend/app will impact the Bazel src/backend package. Any two pull requests that share an
impacted target must be tested together; otherwise, they can be tested independently.
We currently support Bazel; other solutions, such as Buck, Nx, etc. are on the way! You may also define your own suite of impacted targets using glob-based targets.
We use Tinder's bazel-diff tool to compute the impacted targets of a particular PR. The tool computes a mapping of package --> hash at the source and dest shas, then reports any packages which have a differing hash.