This message was deleted.

thanks for reaching out! this is a case that we're thinking about improving -- providing better separation between activity in multiple github organizations i can confirm that in your current setup, your activity (submits/reviews/merges) will only count towards the org they happen in, so cinder will not be billed for your personal use of graphite unfortunately we haven't added support for installing the slack integration on multiple workspaces yet, but this is something we're considering soon!

Thanks for the reply! Good to know about submit/review/merge charges. To clarify, the Slack problem wasn't that I wanted to install the Slack integration on multiple Slack workspaces. The issue was that the Graphite Slack bot in Cinder's Slack workspace was posting messages from my personal repo! Even if I'm the only one who sees it in the Slack UI, I'm unclear whether Slack admins would have visibility and that's worrying. I'm not sure if that's a Graphite Slack integration bug or an issue with how my Graphite CLI auth was set up.

totally makes sense! to be clear, by multi-workspace support i meant allowing you to specify where notifications from each org should go (potentially to different workspaces) glad this works for you now though!

Ah. In that case it sounds like the only way to prevent that from happening is to uninstall the Graphite Slack integration from the Cinder Slack

correct

Thanks so much for the answers! Very helpful.