From a546975361c5a52224289b49e2589683c2122c42 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 16 Apr 2026 11:06:59 +0000 Subject: [PATCH] docs(flaky-tests): clarify default stable branch recognition Trunk now automatically recognizes main, master, and develop as stable branches for upload classification. Reflect this in the getting started prerequisites and add a hint for repos using other branch names. Source: trunk-io/trunk2#3555 Co-Authored-By: Claude Opus 4.6 --- flaky-tests/get-started/README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/flaky-tests/get-started/README.md b/flaky-tests/get-started/README.md index 1ae4400b..f600bba3 100644 --- a/flaky-tests/get-started/README.md +++ b/flaky-tests/get-started/README.md @@ -12,7 +12,7 @@ Trunk Flaky Tests detects flaky tests by analyzing test results from your CI run * Account at [app.trunk.io](https://app.trunk.io) * Ability to modify repository CI configuration and add secrets -* Tests running in CI on both PRs and stable branches (e.g., main) +* Tests running in CI on both PRs and stable branches (e.g., main, master, or develop) #### Step 1: Ensure JUnit XML output @@ -35,6 +35,10 @@ Add test result uploads to all CI jobs that run tests. Uploads from both PRs and stable branches are required for Trunk Flaky Tests to accurately detect flaky tests. +{% hint style="info" %} +Trunk automatically recognizes `main`, `master`, and `develop` as stable branches. If your primary branch uses a different name, configure uploads from that branch the same way and Trunk will classify it correctly based on how your monitors are scoped. +{% endhint %} + #### Step 3: Verify integration 1. Push your changes and trigger a CI run