Skip to content

trunk-merge/pr-449/97d48440-2db0-4c9d-b861-4ea56a6df15d#450

Closed
trunk-staging-io[bot] wants to merge 2 commits intomainfrom
trunk-merge/pr-449/97d48440-2db0-4c9d-b861-4ea56a6df15d
Closed

trunk-merge/pr-449/97d48440-2db0-4c9d-b861-4ea56a6df15d#450
trunk-staging-io[bot] wants to merge 2 commits intomainfrom
trunk-merge/pr-449/97d48440-2db0-4c9d-b861-4ea56a6df15d

Conversation

@trunk-staging-io
Copy link

Trunk Merge Pull Request Banner

This pull request was created and is being managed by Trunk Merge.

This pull request is based on the main branch at SHA 02c7816c4f838bbf3c034dac2b1f53bbf873542a.

See more details here.

When CI completes, this pull request will be closed automatically.

Pull Requests Being Tested

This pull request is testing the changes from pull request 449.

claude and others added 2 commits March 6, 2026 17:31
Document how Trunk Merge Queue can run alongside GitHub Merge Queue
during a gradual migration. Covers:
- No disruption to existing workflows
- Disabling comments during evaluation
- How Trunk handles external merges gracefully

Slack thread: https://trunk-io.slack.com/archives/C06973UPDU7/p1772817954315439

https://claude.ai/code/session_01XiND81kmk2wy4dMLxEYnJp
@trunk-staging-io trunk-staging-io bot closed this Mar 6, 2026
@trunk-staging-io trunk-staging-io bot deleted the trunk-merge/pr-449/97d48440-2db0-4c9d-b861-4ea56a6df15d branch March 6, 2026 19:02
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