Skip to content

docs(flaky-tests): include the test collection ID wherever uploads are set up - #379

Merged
TylerJang27 merged 4 commits into
mainfrom
tyler/require-test-collection-id
Sep 30, 2026
Merged

TylerJang27 merged 4 commits into
mainfrom
tyler/require-test-collection-id

Conversation

@TylerJang27

@TylerJang27 TylerJang27 commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Summary

test-collections.mdx says the collection ID and org slug are both required, but several setup pages still showed uploads with only a slug and token. This treats the ID as required everywhere uploads are set up. The ID is not a secret, so the examples put it directly in the upload command as <TRUNK_TEST_COLLECTION_ID> rather than having readers store it as a CI variable.

  • CLI reference:
    • The "Organization Slug and Token" section names the ID alongside the slug and token.
    • Every upload and test example passes --test-collection-id.
    • The flag table marks it Required.
    • The Test Collections section no longer frames the ID as opt-in.
  • All 13 CI provider pages:
    • Every upload command, the RSpec tabs included, passes the ID inline. On pages that previously read it from an undefined variable ($TRUNK_TEST_COLLECTION_ID, $(…), ${bamboo.…}, ${{ vars.… }}), it is now inline too.
    • The first setup step lists the collection ID.
    • A short Test Collection ID subsection says where to copy it from and that it can go straight into the command.
    • The troubleshooting line also asks readers to check the collection ID.
    • Heading anchors are unchanged, since other pages link to them.
  • Other CI: the example script now ends with an actual upload command.
  • Google Cloud Build: the placeholder table lists <TRUNK_TEST_COLLECTION_ID>.
  • Quarantining: both GitHub Actions examples pass test-collection-id. Every analytics-uploader example in the docs now carries the ID except the fork-PR page's public-repo-id example, which by design uploads to a repository rather than a collection.
  • MCP reference: set-up-test-uploads documents the new testCollectionId parameter, and the Claude Code plugin's /trunk:setup-uploads description mentions choosing a collection. These describe trunk-io/trunk2#6581, so merge them after it deploys.

mint broken-links reports nothing new.

🤖 Generated with Claude Code

…e set up

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@mintlify

mintlify Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
trunk 🟢 Ready View Preview Sep 30, 2026, 5:53 PM

…ples

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…a CI variable

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@TylerJang27
TylerJang27 merged commit 356983b into main Sep 30, 2026
2 checks passed
@mintlify

mintlify Bot commented Sep 30, 2026

Copy link
Copy Markdown
Contributor

Docs PR opened: #380

Added a changelog post saying the MCP setup tool and Claude Code plugin now set up uploads for a test collection.

This branch was successfully deployed

1 active deployment
staging — e8240508 Deployed Sep 30, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant