Slack Integration
Push updates about your merge queue status to a Slack channel to keep your team informed.
Trunk Merge Queue integrates with Slack to send real-time notifications about queue activity and pull request state changes to a designated channel.
Setup integration with Slack
After you have Merge Queue set up and running in your repository, you can configure Slack notifications to receive alerts for various queue events.
Enable Merge Queue Notifications
Navigate to
Settings > Repositories > [your repository] > Merge QueueFind the Connect with Slack setting and click Connect to install the Trunk Slack application
Authorize the app to post to your desired channel
You'll be redirected back to your settings page once authorization is complete
Configuring Notification Preferences
After connecting to a Slack channel, you can customize which notifications you want to receive. By default, all Merge Queue notifications are enabled.
Merge is updated
The merge queue's configuration was changed. This covers anything that changes how the queue acts, including: pausing or draining the queue, changing its mode, changing testing concurrency, and so on.
Pull request is submitted for merging
A pull request has been submitted to the queue
Pull request is ready for testing
A pull request has been admitted to the queue and will begin testing as soon as it can
Pull request is testing
Trunk merge has begun testing a pull request
Pull request has passed tests
Testing has passed on a pull request. The PR will be merged when it reached the top of the queue
Pull request is merged
A pull request submitted to the queue has successfully been merged into its target branch
Pull request fails
Testing failed on a pull request and it was removed from the queue or Trunk failed to merge the PR into its target branch
Pull request is canceled
A pull request has been canceled, either manually or due to it reaching a configured testing timeout
Pull request is waiting for earlier pull requests
A pull request failed testing, but the pull request is currently waiting before being kicked. This can happen for one of two reasons: 1. The pull request is not at the head of the queue, so it is waiting to determine if it is the source of the failure or if a PR it depends on is 2. Pending Failure Depth is enabled and the PR is waiting for other PRs below it to finish testing
Last updated