# Trunk Platform > Trunk is building the outer loop platform for engineers and coding agents. Make software delivery cheaper, faster, and more reliable with Merge Queue, Flaky Tests, CI Intelligence, and Dynamic CI. Cut compute costs, eliminate wasted work, and keep pull requests moving as code volume grows. ## Overview - [Trunk Platform](https://docs.trunk.io/index.md): Ship Software as Fast as AI Writes It ## Merge Queue ### Merge Queue - [Overview](https://docs.trunk.io/merge-queue/merge-queue.md): Trunk Merge Queue runs unrelated PRs in independent test lanes instead of one serial line, keeps merging when a flaky test would stall the queue, and batches changes to cut CI runs. - [Migrate from GitHub Merge Queue](https://docs.trunk.io/merge-queue/migrating-from-github-merge-queue.md): Switch from GitHub's native merge queue to Trunk Merge Queue with minimal disruption to your workflow. - [Integration for Slack](https://docs.trunk.io/merge-queue/integration-for-slack.md): Send merge queue updates to multiple Slack channels and receive personal DM notifications — all powered by the Trunk Slack app. - [Browser Extensions](https://docs.trunk.io/merge-queue/browser-extensions.md): Submit, cancel, and track Trunk Merge Queue pull requests directly from GitHub with the Trunk browser extension for Chrome and Firefox. Optionally shows Flaky Tests results inline on the PR page. - [CLI reference](https://docs.trunk.io/merge-queue/reference/merge-queue-cli-reference.md): Trunk CLI commands for submitting, canceling, pausing, and resuming the merge queue. - [Webhooks](https://docs.trunk.io/merge-queue/webhooks.md): Reference for Trunk Merge Queue webhook events, lifecycle, and payload behavior. - [API reference](https://docs.trunk.io/links/merge-queue-api.md) - [Changelog](https://docs.trunk.io/merge-queue/changelog.md): Recent updates to Trunk Merge Queue. #### Getting Started - [Getting Started](https://docs.trunk.io/merge-queue/getting-started.md): Set up Trunk Merge Queue for your repository by installing the GitHub App, creating a queue, and configuring branch protection. - [Install and create your queue](https://docs.trunk.io/merge-queue/getting-started/install-and-create-your-queue.md): Install the Trunk GitHub App, connect your repository, and create your first merge queue. - [Configure branch protection](https://docs.trunk.io/merge-queue/getting-started/configure-branch-protection.md): Set up GitHub branch protection so Trunk Merge Queue can admit, test, and merge pull requests through your protected branch. - [Configure CI status checks](https://docs.trunk.io/merge-queue/getting-started/configure-ci-status-checks.md): Make sure your CI runs whenever Trunk Merge Queue tests a pull request. - [Test your setup](https://docs.trunk.io/merge-queue/getting-started/test-your-setup.md): Verify your Trunk Merge Queue installation by submitting a test PR and confirming it merges automatically. ##### GitLab - [GitLab](https://docs.trunk.io/merge-queue/getting-started/gitlab.md): Set up Trunk Merge Queue for a GitLab project by connecting a GitLab group, creating a queue, and configuring protected branches and CI pipelines. #### Optimizations - [Optimizations](https://docs.trunk.io/merge-queue/optimizations.md): Advanced features that increase merge throughput, handle flaky tests, and prioritize critical PRs in Trunk Merge Queue. - [Predictive testing](https://docs.trunk.io/merge-queue/optimizations/predictive-testing.md): Test PRs against the projected future state of your main branch to catch conflicts before they reach production. - [Anti-flake protection](https://docs.trunk.io/merge-queue/optimizations/anti-flake-protection.md): Combine optimistic merging and pending failure depth to prevent flaky test failures from blocking the merge queue. - [Batching](https://docs.trunk.io/merge-queue/optimizations/batching.md): Test multiple PRs together as a single unit to increase merge throughput and reduce CI costs. - [Priority merging](https://docs.trunk.io/merge-queue/optimizations/priority-merging.md): Fast-track critical PRs like hotfixes and security patches to the front of the merge queue. - [Optimistic merging](https://docs.trunk.io/merge-queue/optimizations/optimistic-merging.md): Merge PRs faster by using passing test results from later PRs in the queue to validate earlier ones. - [Pending failure depth](https://docs.trunk.io/merge-queue/optimizations/pending-failure-depth.md): Keep failed PRs in the queue while successor PRs test, giving transient failures a chance to pass. - [Direct merge to main](https://docs.trunk.io/merge-queue/optimizations/direct-merge-to-main.md): Skip redundant retesting and merge PRs directly when they are already tested against the current tip of main. ##### Parallel queues - [Parallel queues](https://docs.trunk.io/merge-queue/optimizations/parallel-queues.md): Create dynamic parallel queues to reduce queue time - [Bazel](https://docs.trunk.io/merge-queue/optimizations/parallel-queues/bazel.md): Instructions for enabling dynamic parallel queues powered by your bazel graph - [Nx](https://docs.trunk.io/merge-queue/optimizations/parallel-queues/nx.md): Instructions for enabling dynamic parallel queues powered by your Nx graph - [API](https://docs.trunk.io/merge-queue/optimizations/parallel-queues/api.md): Upload impacted targets, read testing details, and handle the common gotchas - [Upload impacted targets from GitHub Actions](https://docs.trunk.io/merge-queue/optimizations/parallel-queues/github-actions.md): Authenticate a GitHub Actions job to the v2 API with no Trunk secret, including fork pull requests in public repositories. #### Using the Queue - [Using the Queue](https://docs.trunk.io/merge-queue/using-the-queue/index.md): Daily operations for working with Trunk Merge Queue. - [Submit and cancel pull requests](https://docs.trunk.io/merge-queue/using-the-queue/reference.md): Covers the journey of a PR from submission through various states to completion - [Stacked pull requests](https://docs.trunk.io/merge-queue/using-the-queue/stacked-pull-requests.md): Merge a chain of dependent pull requests as a single unit - [Monitor queue status](https://docs.trunk.io/merge-queue/using-the-queue/monitor-queue-status.md): View real-time queue activity, PR status, and test results in the Trunk Merge Queue dashboard. - [Handle failed pull requests](https://docs.trunk.io/merge-queue/using-the-queue/handle-failed-pull-requests.md): Understand why PRs fail in the merge queue and how to fix and resubmit them. - [Emergency pull requests](https://docs.trunk.io/merge-queue/using-the-queue/emergency-pull-requests.md): Bypass the merge queue entirely for true emergencies. Use with caution as this can invalidate in-progress queue tests. - [Automate the queue with the API](https://docs.trunk.io/merge-queue/using-the-queue/api.md): Submit pull requests, wait for merges, and read queue order with the API. #### Direct-to-Queue - [Overview](https://docs.trunk.io/merge-queue/using-the-queue/direct-to-queue.md): Admins can send a pull request directly to Merge Queue even when GitHub branch protection rules aren't satisfied. The PR is still tested; only the final merge bypasses protection. - [Configuration](https://docs.trunk.io/setup-and-administration/trunk-sudo-app.md): Instrucions to setup and configure the Direct-to-Queue capability of the Merge Queue. #### Administration - [Administration](https://docs.trunk.io/merge-queue/administration/index.md): Configuration, integrations, and analytics for queue administrators. - [Settings and configurations](https://docs.trunk.io/merge-queue/administration/advanced-settings.md): Explanation of settings for states, timeouts, concurrency, and branch protection. - [Terraform Provider](https://docs.trunk.io/merge-queue/administration/terraform.md): Manage Trunk Merge Queue configuration as code using the trunk-io/trunk Terraform provider. - [Migrate to Terraform provider 2.0](https://docs.trunk.io/merge-queue/administration/terraform-migrate-to-2.md): Upgrade the trunk-io/trunk Terraform provider from 1.x to 2.0, and optionally move from the organization API token to an API key. - [Metrics and monitoring](https://docs.trunk.io/merge-queue/administration/metrics.md): Monitor Trunk Merge Queue throughput, wait times, and health with built-in metrics. #### Reference - [Reference](https://docs.trunk.io/merge-queue/reference/index.md): Technical documentation and troubleshooting resources. - [FAQ](https://docs.trunk.io/merge-queue/reference/common-problems.md): Answers to common questions about Trunk Merge Queue behavior and the PR lifecycle. - [Troubleshooting](https://docs.trunk.io/merge-queue/reference/troubleshooting.md): Common Trunk Merge Queue issues and how to fix them, including permission errors, stuck PRs, and missing status checks. - [GitHub API failures](https://docs.trunk.io/merge-queue/reference/github-api-failures.md): What to do when a PR fails to merge because of GitHub server errors, rate limits, or rejected merge calls. ## Tests ### Flaky Tests - [Changelog](https://docs.trunk.io/flaky-tests/changelog.md): Recent updates to Trunk Flaky Tests. #### Overview - [Overview](https://docs.trunk.io/flaky-tests/overview.md): Detect, quarantine, and eliminate flaky tests from your codebase - [Test Collections](https://docs.trunk.io/flaky-tests/test-collections.md): Group tests into named collections, each with its own flake detection, quarantining, and ticketing settings. - [Dashboard](https://docs.trunk.io/flaky-tests/dashboard.md): Learn to find flaky tests and understand their impact using the Flaky Tests dashboard #### Getting Started - [Getting Started](https://docs.trunk.io/flaky-tests/get-started/index.md): Set up Trunk Flaky Tests by creating a test collection, configuring test result output, uploading from CI, and enabling flake detection monitors. - [Trunk CLI](https://docs.trunk.io/flaky-tests/get-started/trunk-cli.md): Install the trunk CLI, store a Trunk API key, and upload test results to Trunk Flaky Tests with trunk flakytests. - [Multiple Repositories and Forks](https://docs.trunk.io/flaky-tests/get-started/multiple-repositories.md): Learn how Trunk identifies repositories, track tests across forks and multiple repositories, and enable test uploads from fork PR workflows. - [Uploads from Forked Pull Requests](https://docs.trunk.io/flaky-tests/get-started/fork-pr-uploads.md): Upload test results and apply quarantining on pull requests from forks, which can't read your repository secrets or your Trunk API key. ##### Test frameworks - [Test frameworks](https://docs.trunk.io/flaky-tests/get-started/frameworks.md): Guides for generating Trunk-compatible test results from various test frameworks - [Android](https://docs.trunk.io/flaky-tests/get-started/frameworks/android.md): A guide for generating Trunk-compatible test reports for Android projects - [Bazel](https://docs.trunk.io/flaky-tests/get-started/frameworks/bazel.md): A guide for generating Trunk-compatible test reports with Bazel - [Behave](https://docs.trunk.io/flaky-tests/get-started/frameworks/behave.md): A guide for generating Trunk-compatible test reports for Behave - [cargo-nextest](https://docs.trunk.io/flaky-tests/get-started/frameworks/rust.md): A guide for generating Trunk-compatible test reports for Rust - [Cypress](https://docs.trunk.io/flaky-tests/get-started/frameworks/cypress.md): A guide for generating Trunk-compatible test reports for Cypress tests - [Dart Test](https://docs.trunk.io/flaky-tests/get-started/frameworks/dart-test.md): A guide for generating Trunk-compatible test reports for Dart tests - [Go](https://docs.trunk.io/flaky-tests/get-started/frameworks/gotestsum.md): A guide for generating Trunk-compatible test reports for Go tests - [GoogleTest](https://docs.trunk.io/flaky-tests/get-started/frameworks/googletest.md): A guide for generating Trunk-compatible test reports for GoogleTest - [Gradle](https://docs.trunk.io/flaky-tests/get-started/frameworks/gradle.md): A guide for generating Trunk-compatible test reports for Gradle - [Jasmine](https://docs.trunk.io/flaky-tests/get-started/frameworks/jasmine.md): A guide for generating Trunk-compatible test reports for Jasmine tests - [Jest](https://docs.trunk.io/flaky-tests/get-started/frameworks/jest.md): A guide for generating Trunk-compatible test reports for Jest tests - [Karma](https://docs.trunk.io/flaky-tests/get-started/frameworks/karma.md): A guide for generating Trunk-compatible test reports for Karma tests - [Kotest](https://docs.trunk.io/flaky-tests/get-started/frameworks/kotest.md): A guide for generating Trunk-compatible test reports for Kotest - [Maven](https://docs.trunk.io/flaky-tests/get-started/frameworks/maven.md): A guide for generating Trunk-compatible test reports for Maven - [minitest](https://docs.trunk.io/flaky-tests/get-started/frameworks/minitest.md): A guide for generating Trunk-compatible test reports for minitest - [Mocha](https://docs.trunk.io/flaky-tests/get-started/frameworks/mocha.md): A guide for generating Trunk-compatible test reports for Mocha - [Nightwatch](https://docs.trunk.io/flaky-tests/get-started/frameworks/nightwatch.md): A guide for generating Trunk-compatible test reports for Nightwatch - [NUnit](https://docs.trunk.io/flaky-tests/get-started/frameworks/nunit.md): A guide for generating Trunk-compatible test reports for NUnit - [Pest](https://docs.trunk.io/flaky-tests/get-started/frameworks/pest.md): A guide for generating Trunk-compatible test reports for Pest - [PHPUnit](https://docs.trunk.io/flaky-tests/get-started/frameworks/phpunit.md): A guide for generating Trunk-compatible test reports for PHPUnit - [Playwright](https://docs.trunk.io/flaky-tests/get-started/frameworks/playwright.md): A guide for generating Trunk-compatible test reports for Playwright - [Pytest](https://docs.trunk.io/flaky-tests/get-started/frameworks/pytest.md): A guide for generating Trunk-compatible test reports for Pytest - [Robot Framework](https://docs.trunk.io/flaky-tests/get-started/frameworks/robot-framework.md): A guide for generating Trunk-compatible test reports for Robot Framework - [Swift Testing](https://docs.trunk.io/flaky-tests/get-started/frameworks/swift-testing.md): A guide for generating Trunk-compatible test reports with Swift Testing - [Testplan](https://docs.trunk.io/flaky-tests/get-started/frameworks/testplan.md): A guide for generating Trunk-compatible test reports for Testplan - [Vitest](https://docs.trunk.io/flaky-tests/get-started/frameworks/vitest.md): A guide for generating Trunk-compatible test reports with Vitest - [XCTest](https://docs.trunk.io/flaky-tests/get-started/frameworks/xctest.md): A guide for generating Trunk-compatible test reports for XCode and xcodebuild - [Other Test Frameworks](https://docs.trunk.io/flaky-tests/get-started/frameworks/other-test-frameworks.md): A guide for generating Trunk-compatible test reports with other test frameworks ###### RSpec - [RSpec](https://docs.trunk.io/flaky-tests/get-started/frameworks/rspec/index.md): A guide for generating Trunk-compatible test reports for RSpec using Trunk's RSpec plugin - [RSpec (Manual Uploads)](https://docs.trunk.io/flaky-tests/get-started/frameworks/rspec/manual-uploads.md): A guide for generating Trunk-compatible test reports for RSpec without using Trunk's RSpec plugin ##### CI Providers - [CI Providers](https://docs.trunk.io/flaky-tests/get-started/ci-providers.md): You can easily integrate Flaky Tests from any CI Provider - [Atlassian Bamboo](https://docs.trunk.io/flaky-tests/get-started/ci-providers/atlassian-bamboo.md): Configure Atlassian Bamboo to upload test results to Trunk Flaky Tests - [Azure DevOps Pipelines](https://docs.trunk.io/flaky-tests/get-started/ci-providers/azure-devops-pipelines.md): Upload test results from Azure DevOps Pipelines to Trunk for flaky test detection. - [BitBucket Pipelines](https://docs.trunk.io/flaky-tests/get-started/ci-providers/bitbucket-pipelines.md): Upload test results from Bitbucket Pipelines to Trunk for flaky test detection. - [Buildkite](https://docs.trunk.io/flaky-tests/get-started/ci-providers/buildkite.md): Configure Buildkite jobs to upload test results to Trunk Flaky Tests - [CircleCI](https://docs.trunk.io/flaky-tests/get-started/ci-providers/circleci.md): Configure CircleCI jobs to upload test results to Trunk Flaky Tests - [Depot CI](https://docs.trunk.io/flaky-tests/get-started/ci-providers/depot-ci.md): Configure Depot CI to upload test results to Trunk Flaky Tests - [Drone CI](https://docs.trunk.io/flaky-tests/get-started/ci-providers/droneci.md): Configure Flaky Tests using Drone CI - [Evergreen](https://docs.trunk.io/flaky-tests/get-started/ci-providers/evergreen.md): Configure Evergreen to upload test results to Trunk Flaky Tests - [GitHub Actions](https://docs.trunk.io/flaky-tests/get-started/ci-providers/github-actions.md): Configure Flaky Tests detection using a GitHub Action - [GitLab](https://docs.trunk.io/flaky-tests/get-started/ci-providers/gitlab.md): Configure Flaky Tests using GitLab CI - [Google Cloud Build](https://docs.trunk.io/flaky-tests/get-started/ci-providers/google-cloud-build.md): Configure Google Cloud Build to upload test results to Trunk Flaky Tests - [Jenkins](https://docs.trunk.io/flaky-tests/get-started/ci-providers/jenkins.md): Configure Flaky Tests using Jenkins - [Semaphore CI](https://docs.trunk.io/flaky-tests/get-started/ci-providers/semaphoreci.md): Configure Flaky Tests using Semaphore CI - [Travis CI](https://docs.trunk.io/flaky-tests/get-started/ci-providers/travisci.md): Configure Flaky Tests using Travis CI - [Other CI Providers](https://docs.trunk.io/flaky-tests/get-started/ci-providers/otherci.md): Configure Flaky Tests using any CI Provider #### Flaky test detection - [Flake Detection](https://docs.trunk.io/flaky-tests/detection/index.md): Learn how Trunk detects and labels flaky and broken tests - [Flag as Flaky](https://docs.trunk.io/flaky-tests/detection/flag-as-flaky.md): Manually mark a test as flaky from the test detail page - [The Importance of PR Test Results](https://docs.trunk.io/flaky-tests/detection/the-importance-of-pr-test-results.md): Why uploading test results from pull requests is required for accurate flaky test detection, quarantining, and impact measurement. - [Infrastructure Failure Protection](https://docs.trunk.io/flaky-tests/detection/infrastructure-failure-protection.md): Prevent false Trunk Flaky Tests detections during CI outages and infrastructure failures. ##### Health classification monitors - [Pass-on-Retry Monitor](https://docs.trunk.io/flaky-tests/detection/pass-on-retry-monitor.md): Detect tests that fail then pass on retry within the same commit - [Failure Rate Monitor](https://docs.trunk.io/flaky-tests/detection/failure-rate-monitor.md): Detect flaky or broken tests based on failure rate over a configurable time window - [Failure Count Monitor](https://docs.trunk.io/flaky-tests/detection/failure-count-monitor.md): Detect flaky or broken tests as soon as they accumulate a configured number of failures ##### Lifecycle & performance monitors - [New Test Monitor](https://docs.trunk.io/flaky-tests/detection/new-test-monitor.md): Track recently added tests and apply labels until they have an established history. - [Skipped Test Monitor](https://docs.trunk.io/flaky-tests/detection/skipped-test-monitor.md): Detect tests that are consistently being skipped and apply labels to surface them for review. - [Slow Test Monitor](https://docs.trunk.io/flaky-tests/detection/slow-test-monitor.md): Flag tests whose duration percentile exceeds a configured threshold. - [Timeout Inflation Monitor](https://docs.trunk.io/flaky-tests/detection/timeout-inflation-monitor.md): Flag tests whose failure times sit far above their passing times, exposing timeouts that have ratcheted up beyond what the test actually needs. #### Flaky test management - [Flaky test management](https://docs.trunk.io/flaky-tests/management/index.md): Organize, triage, and coordinate follow-up for detected flaky tests. - [Managing detected flaky tests](https://docs.trunk.io/flaky-tests/management/managing-detected-flaky-tests.md): A step-by-step guide for building an automated process to manage detected flaky tests. - [Test Labels](https://docs.trunk.io/flaky-tests/management/test-labels.md): Organize and categorize test cases with organization-scoped labels. ##### Ticketing - [Ticketing](https://docs.trunk.io/flaky-tests/management/ticketing.md): Triage your flaky tests faster by creating automatically assigned and labeled tickets in your ticketing system - [Automatic ticketing](https://docs.trunk.io/flaky-tests/management/ticketing/automatic-ticketing.md): Automatically create, reopen, and close tickets as your tests change status — no webhooks or custom automation required - [Asana integration](https://docs.trunk.io/flaky-tests/management/ticketing/asana-integration.md): Triage your flaky tests faster by creating automatically assigned and labeled tasks with the Asana integration - [Jira integration](https://docs.trunk.io/flaky-tests/management/ticketing/jira-integration.md): Triage your flaky tests faster by creating automatically assigned and labeled tickets with the Jira integration - [Jira Data Center integration](https://docs.trunk.io/flaky-tests/management/ticketing/jira-data-center-integration.md): Create, link, and automate tickets for flaky tests in your self-managed Jira Data Center instance - [Linear integration](https://docs.trunk.io/flaky-tests/management/ticketing/linear-integration.md): Triage your flaky tests faster by creating automatically assigned and labeled tickets with the Linear integration - [Other ticketing platforms](https://docs.trunk.io/flaky-tests/management/ticketing/other-ticketing-platforms.md): Triage your flaky tests faster by manually creating tickets from generated markdown #### Quarantining - [Quarantining](https://docs.trunk.io/flaky-tests/quarantining/index.md): Mitigate impact of known flaky tests by isolating them at run time - [Quarantine Service Availability](https://docs.trunk.io/flaky-tests/quarantining/quarantine-service-availability.md): How Trunk Analytics CLI handles quarantine service outages without compromising your CI pipeline. #### Webhooks - [Webhooks](https://docs.trunk.io/flaky-tests/webhooks/index.md): Use webhooks to automate custom flaky test workflows - [Integration for Slack](https://docs.trunk.io/flaky-tests/webhooks/slack-integration.md): Learn how to use flaky test webhooks to power Slack notifications - [Microsoft Teams integration](https://docs.trunk.io/flaky-tests/webhooks/microsoft-teams-integration.md): Send flaky test alerts to Microsoft Teams using Trunk Flaky Tests webhooks. - [GitHub Issues integration](https://docs.trunk.io/flaky-tests/webhooks/github-issues-integration.md): Learn how to automatically create GitHub Issues with Flaky Tests webhooks - [Linear integration](https://docs.trunk.io/flaky-tests/webhooks/linear-integration.md): Learn how to automatically create Linear issues with Flaky Tests webhooks - [Jira integration](https://docs.trunk.io/flaky-tests/webhooks/jira-integration.md): Learn how to automatically create Jira issues with Flaky Test webhooks #### Recipes - [Recipes](https://docs.trunk.io/flaky-tests/recipes.md): Step-by-step guides that use Trunk's API, webhooks and MCP server to fix flaky tests, guard your CI, and keep teams informed. - [Fix Flaky Tests](https://docs.trunk.io/flaky-tests/recipes/autofix-flaky-tests.md): Give a coding agent the context it needs to fix a flaky test, from Trunk's API. - [Autofix CI Failures](https://docs.trunk.io/flaky-tests/recipes/autofix-ci-failures.md): Have a coding agent investigate a red CI run with Trunk's MCP server and open a pull request that fixes it. - [Tighten Test Timeouts](https://docs.trunk.io/flaky-tests/recipes/tighten-test-timeouts.md): Find tests whose timeouts sit far above their passing runtime, and have a coding agent propose tighter values. - [Evaluate Release Branch Test Health](https://docs.trunk.io/flaky-tests/recipes/release-branch-test-health.md): Have an agent report the flaky and failing tests on a release branch before you cut a release. - [Never Quarantine Tests in Protected Paths](https://docs.trunk.io/flaky-tests/recipes/never-quarantine-protected-paths.md): Keep every test under the paths you choose out of quarantine, including tests added later and overrides people change by hand. - [Explain a Failed Pull Request](https://docs.trunk.io/flaky-tests/recipes/explain-failed-pr-tests.md): Comment on a red pull request with which failed tests are known to be flaky and which are probably real. - [Route Flaky Tests to Their Owners](https://docs.trunk.io/flaky-tests/recipes/route-flaky-tests-to-owners.md): When a test turns flaky, file a ticket for its code owners and tell their team in Slack - [Alert When a Test Escalates](https://docs.trunk.io/flaky-tests/recipes/alert-on-test-escalation.md): Send Slack alerts when a test gets worse, not just the first time it's flagged - [Post a Weekly Flaky Test Digest](https://docs.trunk.io/flaky-tests/recipes/weekly-triage-digest.md): Every week, post the tests that turned flaky, broken or healthy to Slack, grouped by owner. #### Reference - [Reference](https://docs.trunk.io/flaky-tests/reference/index.md): Reference documentation for Flaky Tests APIs, CLI commands, and MCP tools. - [CLI Reference](https://docs.trunk.io/flaky-tests/reference/cli-reference.md): CLI tool for uploading test results to Trunk from CI, enabling flaky test detection and quarantining. - [API reference](https://docs.trunk.io/links/flaky-tests-api.md) ##### MCP reference - [Use MCP Server](https://docs.trunk.io/flaky-tests/reference/mcp-reference.md): Use the Trunk MCP server from your IDE or AI application to access flaky test insights and configure test uploads - [Search Test](https://docs.trunk.io/flaky-tests/reference/mcp-reference/search-test.md): MCP tool reference: search-test - [List Test Collections](https://docs.trunk.io/flaky-tests/reference/mcp-reference/list-test-collections.md): MCP tool reference: list-test-collections - [Set up test uploads](https://docs.trunk.io/flaky-tests/reference/mcp-reference/set-up-test-uploads.md): MCP tool reference: setup-trunk-uploads - [Investigate CI Failure](https://docs.trunk.io/flaky-tests/reference/mcp-reference/investigate-ci-failure.md): MCP tool reference: investigate-ci-failure ###### Configuration - [Configuration](https://docs.trunk.io/flaky-tests/reference/mcp-reference/configuration/index.md): Configure your AI application to connect to the Trunk MCP server for flaky test insights and setup assistance. - [Cursor (IDE)](https://docs.trunk.io/flaky-tests/reference/mcp-reference/configuration/cursor-ide.md): Add Trunk's MCP Server to Cursor - [GitHub Copilot (IDE)](https://docs.trunk.io/flaky-tests/reference/mcp-reference/configuration/github-copilot-ide.md): Add Trunk's MCP Server to GitHub Copilot - [Claude Code (CLI)](https://docs.trunk.io/flaky-tests/reference/mcp-reference/configuration/claude-code-cli.md): Add Trunk's MCP Server to Claude Code - [Claude Code Plugin](https://docs.trunk.io/flaky-tests/reference/mcp-reference/configuration/claude-code-plugin.md): Install the Trunk plugin for Claude Code - [Gemini (CLI)](https://docs.trunk.io/flaky-tests/reference/mcp-reference/configuration/gemini-cli.md): Add Trunk's MCP Server to Gemini - [Bearer Authentication](https://docs.trunk.io/flaky-tests/reference/mcp-reference/configuration/bearer-auth.md): Add Trunk's MCP Server via Bearer Authentication ## Dynamic CI ### Overview - [Trunk Dynamic CI](https://docs.trunk.io/ci/dynamic-ci.md): Run only the CI jobs a pull request needs, decided from your own CI history. - [Getting started](https://docs.trunk.io/ci/dynamic-ci/getting-started/index.md): Set up Trunk, add Dynamic CI to your CI provider, then turn on enforcement. - [Merge queues](https://docs.trunk.io/ci/dynamic-ci/merge-queue.md): How Dynamic CI behaves when your merge queue tests a pull request. - [Run jobs on the head commit before a pull request enters the merge queue](https://docs.trunk.io/ci/dynamic-ci/run-before-queue.md): Have Trunk start the jobs Dynamic CI skipped on a pull request's head commit before the pull request enters the merge queue. - [Force Dynamic CI jobs to run from GitHub, Trunk, or the API](https://docs.trunk.io/ci/dynamic-ci/force-run.md): Use the Trunk browser extension for Chrome and Firefox, the Trunk web app, or the API to mark a Dynamic CI job as Force Run on a pull request. ### CI providers - [GitHub Actions](https://docs.trunk.io/ci/dynamic-ci/getting-started/github-actions.md): Adding Dynamic CI to your existing GitHub Actions workflows - [BuildKite](https://docs.trunk.io/ci/dynamic-ci/getting-started/buildkite.md): Add the Dynamic CI plugin to a Buildkite pipeline. ### Configuration - [Configure how Dynamic CI schedules each CI job](https://docs.trunk.io/ci/dynamic-ci/configuration/jobs.md): Find a job in the Trunk app and set its schedule for pull requests and the merge queue. - [Skip single variations of a matrix job](https://docs.trunk.io/ci/dynamic-ci/configuration/matrices.md): Opt a matrix job in to being decided variation by variation, and choose the keys that group it. - [Signals Dynamic CI uses to decide](https://docs.trunk.io/ci/dynamic-ci/configuration/signals.md): The kinds of evidence Dynamic CI combines into a run or skip verdict for each job. - [Path filters](https://docs.trunk.io/ci/dynamic-ci/configuration/path-filters.md): Tell Dynamic CI which changed files are relevant to each job. - [Roll out Dynamic CI with Learning and Enforced modes](https://docs.trunk.io/ci/dynamic-ci/configuration/mode.md): Choose Learning or Enforced mode for each repository, and use the Learning mode allow list to enforce Dynamic CI for selected engineers or GitHub labels. ### Reference - [Dynamic CI Action Reference](https://docs.trunk.io/ci/dynamic-ci/dynamic-ci-action-reference.md): Inputs, outputs, and fail-open behavior of the trunk-io/dynamic-ci GitHub Action. - [FAQ](https://docs.trunk.io/ci/dynamic-ci/faq.md): Reliability, forks, and other common questions about Dynamic CI. ## Runners ### Overview - [Trunk Runners](https://docs.trunk.io/runners.md): Fast, reliable, affordable runners for GitHub Actions. - [Get started](https://docs.trunk.io/runners/getting-started.md): Turn on Trunk Runners, choose your machine size, and run your first job. - [Pricing](https://docs.trunk.io/runners/pricing.md): Usage-based pricing for compute, memory, and storage. ### GitHub Actions - [The runs-on label](https://docs.trunk.io/runners/actions/runs-on.md): One label selects a Trunk runner and sets its options. - [Machine sizes](https://docs.trunk.io/runners/actions/sizes.md): Choose CPUs with size and memory per CPU with memory. - [Templates](https://docs.trunk.io/runners/actions/templates.md): Prebake your setup steps into a Trunk Runner template so GitHub Actions jobs start ready and run faster. ### Caching - [Caching](https://docs.trunk.io/runners/cache/index.md): The shared cache lets jobs reuse build results, so they finish faster. - [Cache settings](https://docs.trunk.io/runners/cache/settings.md): Configure the Trunk Runners shared cache for your organization or per repository, including which branches a job can read cache from. ### Organization settings - [Quota and runner priority](https://docs.trunk.io/runners/settings/limits-and-priority.md): How the Trunk Runners CPU quota works and how to mark branches as priority so their jobs start first. ### Reference - [runs-on label reference](https://docs.trunk.io/runners/reference/runs-on-grammar.md): The full Trunk Runners runs-on label format in one table, with examples. - [Setup (168 pages)](https://docs.trunk.io/_llms/setup.txt): Setup, Integrations, Legacy. - [API Reference (148 pages)](https://docs.trunk.io/_llms/api-reference.txt): Getting started, Resources, Beta. - [Changelog (211 pages)](https://docs.trunk.io/_llms/changelog.txt): 2026, 2025, 2024, 2023. ## Other - [CLAUDE](https://docs.trunk.io/CLAUDE.md) - [Manual Setup](https://docs.trunk.io/code-quality/ci-setup/general.md): How to integrate Trunk Code Quality into CI for GitLab and other non-GitHub providers, or for GitHub without using the Trunk GitHub App - [GitHub Integration](https://docs.trunk.io/code-quality/ci-setup/get-started.md): Automate your code quality enforcement with just a few clicks. - [Code Quality CLI](https://docs.trunk.io/code-quality/overview/cli/getting-started.md) - [Actions](https://docs.trunk.io/code-quality/overview/cli/getting-started/actions.md) - [Git Hooks](https://docs.trunk.io/code-quality/overview/cli/getting-started/actions/git-hooks.md): Trunk supports triggering actions on all githooks - [Announce](https://docs.trunk.io/code-quality/overview/cli/getting-started/announce.md) - [Caching](https://docs.trunk.io/code-quality/overview/cli/getting-started/caching.md) - [Code Quality](https://docs.trunk.io/code-quality/overview/cli/getting-started/code-quality.md): CLI Metalinter and VSCode extension for over 100 code checking tools. - [Commands reference](https://docs.trunk.io/code-quality/overview/cli/getting-started/commands-reference.md) - [Actions](https://docs.trunk.io/code-quality/overview/cli/getting-started/commands-reference/actions.md) - [Code Quality](https://docs.trunk.io/code-quality/overview/cli/getting-started/commands-reference/code-quality.md) - [Compatibility](https://docs.trunk.io/code-quality/overview/cli/getting-started/compatibility.md) - [Configuration](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration.md) - [Actions](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/actions.md) - [Logging and Troubleshooting](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/actions/logging-and-troubleshooting.md): Diagnosing problems with actions - [Notifications](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/actions/notifications.md): Trunk Actions can also produce notifications to display in your terminal or in the VSCode extension! - [Lint](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/lint.md) - [Auto-Enable](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/lint/auto-enable.md) - [Commands](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/lint/commands.md) - [Definitions](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/lint/definitions.md) - [Dependencies](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/lint/dependencies.md) - [Files and Caching](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/lint/files-and-caching.md) - [Output](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/lint/output.md) - [Output Parsing](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/lint/output-parsing.md) - [Merge](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/merge.md) - [Per User Overrides](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/per-user-overrides.md) - [Plugins](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/plugins.md) - [Exporting linter configs](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/plugins/exported-configs.md): Reusing linter configs across projects. - [Share config between codebases](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/plugins/external-repositories.md): Sharing configuration between codebases using public config repos - [Runtimes](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/runtimes.md) - [Telemetry](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/telemetry.md) - [Tools](https://docs.trunk.io/code-quality/overview/cli/getting-started/configuration/tools.md) - [Tools](https://docs.trunk.io/code-quality/overview/cli/getting-started/tools.md) - [Migration Guide](https://docs.trunk.io/code-quality/overview/prevent-new-issues/migration-guide.md) - [Overview](https://docs.trunk.io/merge-queue/direct-to-queue/overview.md): Admins can send a pull request directly to Merge Queue even when GitHub branch protection rules aren't satisfied. The PR is still tested; only the final merge bypasses protection. - [Trunk CI](https://docs.trunk.io/setup-and-administration/github-app-permissions.md): GitHub permissions the Trunk CI app requests and what Trunk uses each one for. ## OpenAPI Specs - [openapi-v2](/openapi-v2.json) - [openapi](/openapi.json) - [openapi-v2beta-runners](/openapi-v2beta-runners.json) - [openapi-v2beta-dynamic-ci](/openapi-v2beta-dynamic-ci.json) > The links below point to documentation indexes. Follow each `/_llms/` index recursively until you reach documentation pages. ## Indexes - [Setup (168 pages)](https://docs.trunk.io/_llms/setup.txt): Setup, Integrations, Legacy. - [API Reference (148 pages)](https://docs.trunk.io/_llms/api-reference.txt): Getting started, Resources, Beta. - [Changelog (211 pages)](https://docs.trunk.io/_llms/changelog.txt): 2026, 2025, 2024, 2023.