Skip to content

[close - superseded by #24] docs: migrate recent changes from trunk-io/docs#13

Closed
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/sync-trunk-docs
Closed

[close - superseded by #24] docs: migrate recent changes from trunk-io/docs#13
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/sync-trunk-docs

Conversation

@mintlify
Copy link
Copy Markdown
Contributor

@mintlify mintlify Bot commented May 15, 2026

Summary

Migrates the two commits landed on trunk-io/docs main after the initial import (2026-05-14).

Changes

  • index.mdx — apply welcome-copy update from (Chore): Fix copy on welcome page docs#663: rewrites the Trunk Flaky Tests paragraph to drop the stack-trace-embedding quarantine framing.
  • flaky-tests/detection/index.mdx, failure-count-monitor.mdx, failure-rate-monitor.mdx, pass-on-retry-monitor.mdx, flaky-tests/management/test-labels.mdx — apply Document automatic label application from monitors docs#656: document the new monitor Action (Classify test status vs Apply labels), introduce the Dry-Running with Labels and Automatic labeling from monitors sections, and reshuffle related copy (resolution behavior, muting, detection type).

Links and code fences adjusted to docs2 conventions (.md → relative .mdx paths, {% hint %}<Info>/<Warning>).

@samgutentag samgutentag changed the title docs: migrate recent changes from trunk-io/docs [ready to merge] docs: migrate recent changes from trunk-io/docs May 19, 2026
@samgutentag
Copy link
Copy Markdown
Member

Verification status (2026-05-19): live

Verified: customers can use this. Ready to publish.

Note: superseded by PR #22. Consider closing.

@samgutentag samgutentag changed the title [ready to merge] docs: migrate recent changes from trunk-io/docs [close - superseded by #24] docs: migrate recent changes from trunk-io/docs May 19, 2026
@samgutentag
Copy link
Copy Markdown
Member

Catchup check (2026-05-19): superseded by #24, recommend closing.

Compared this PR's tree against current main:

Recommend closing. PR #22 covers the one remaining upstream PR (trunk-io/docs#657: delete stacked-pull-requests page) that #24 did not.

@samgutentag samgutentag added the ready to merge Verify docs PR: customers can use this. Ready to publish. label May 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready to merge Verify docs PR: customers can use this. Ready to publish.

Development

Successfully merging this pull request may close these issues.

1 participant