Skip to content

feat(signals): add option for default team channel for signals notifications#2487

Merged
joshsny merged 2 commits into
mainfrom
signals-team-default-notification-channel
Jun 5, 2026
Merged

feat(signals): add option for default team channel for signals notifications#2487
joshsny merged 2 commits into
mainfrom
signals-team-default-notification-channel

Conversation

@joshsny
Copy link
Copy Markdown
Contributor

@joshsny joshsny commented Jun 4, 2026

This adds a default channel for inbox notifications for your team to post all signal reports to. Users can override with their own channel for high priority notifications.

Screenshot 2026-06-04 at 18 00 40

Expose the team-level default Slack channel
(SignalTeamConfig.slack_notification_channel) in the inbox
configuration, editable by org admins, alongside the existing per-user
notification channel. Both options are explained in the UI.

Extracts a shared SlackChannelCombobox so the team-default and per-user
pickers reuse one implementation. The team channel lists from the team's
first slack integration, matching how the backend resolves the
integration at send time.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Jun 4, 2026

Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
apps/code/src/renderer/features/settings/components/SlackChannelCombobox.tsx:213-215
**Trigger icon always shows `Hash` for private channels**

The trigger button hardcodes `Hash` regardless of whether the saved channel is private. The current target value format (`channelId|#channelName`) doesn't carry privacy info, so the trigger can't distinguish. Compound this with `configuredSlackChannelOption` always setting `is_private: false` — even the synthesised dropdown entry for a previously-saved private channel will show `Hash` instead of `Lock` until the API response arrives and replaces it. The practical effect is that users with a private channel configured see a misleading public icon in both the trigger and the initial dropdown render.

Reviews (1): Last reviewed commit: "default notifications ui for team" | Re-trigger Greptile

@joshsny joshsny force-pushed the signals-team-default-notification-channel branch from 12b710c to d776d7a Compare June 4, 2026 16:26
@joshsny joshsny requested a review from a team June 4, 2026 17:01
@joshsny joshsny merged commit a7937a8 into main Jun 5, 2026
18 checks passed
@joshsny joshsny deleted the signals-team-default-notification-channel branch June 5, 2026 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants