feat: Reset manual topic changes in incident channels#260
Merged
Conversation
e42aca7 to
eadf647
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit eadf647. Configure here.
taylor-osler-sentry
approved these changes
Jun 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Adds a Slack event handler that reverts manual topic edits in incident channels back to the Firetower-managed topic and sends the editor an ephemeral explaining the reset, quoting what they tried to set, and pointing them to /ft subject, /ft severity, and /ft captain to change incident details instead. This is firetower's first Socket Mode event subscription (message.channels/message.groups), so a no-op catch-all suppresses unhandled-message log spam; a bot-author guard prevents reset loops; and an in-memory event-id cache dedups Slack redeliveries (correct as long as the firetower-slack-app service stays single-instance). User-supplied topic text is escaped before it goes into the ephemeral.
Tested in test env. Just need to update prod manifest for new events.