One Microsoft Teams channel per pull request
A dedicated, ephemeral Microsoft Teams channel for each open PR - auto-created on PR open, auto-archived on merge or close. The PR conversation lives where the PR lives.
Targeting: microsoft teams pr channels ยท 5-minute setup ยท Works alongside the official @github bot
PR conversations get lost in shared channels
When 30 PRs share one Microsoft Teams channel, the conversation about PR #1234 is impossible to follow. Per-PR channels solve this - but they create channel sprawl unless they auto-archive. PullNotifier's upcoming per-PR Microsoft Teams channels feature does both.
How it works in Microsoft Teams
Enable per-PR channels for selected repos.
On PR open, a dedicated Microsoft Teams channel is created with PR metadata pinned.
Reviewers and assignees are auto-invited.
On merge or close, the channel auto-archives - keeping the workspace clean.
Why teams pick PullNotifier for this
Channel per PR
Every PR gets its own Microsoft Teams channel for focused discussion.
Auto-invite reviewers
PR assignees and reviewers are auto-added to the dedicated channel.
Auto-archive on merge
Microsoft Teams workspace stays clean - channels disappear when the PR is closed.
Selective rollout
Enable per-PR channels for high-impact repos only. Keep the simpler routing for the rest.
Related Microsoft Teams features
Frequently asked
When will per-PR Microsoft Teams channels ship?
In active development. Reach out to gabriel@manta.so to join the early access list.
Will this create Microsoft Teams channel sprawl?
No - channels auto-archive on PR merge or close. Microsoft Teams handles archived channels gracefully so the workspace stays clean.
Can I enable this for specific repos only?
Yes. Per-PR channels are opt-in per repository, so you can use them for high-impact repos only.
How does this compare to Axolo's per-PR channels?
Similar concept. Axolo's Microsoft Teams support is in private early access; PullNotifier's per-PR channels are coming as part of the GA roadmap.