Open
Conversation
hrygo
force-pushed
the
feat/slack-permission-policy-v2
branch
2 times, most recently
from
ad56d1f to
9a86e4d
Compare
added 3 commits
February 25, 2026 05:13
- Add DMPolicy and GroupPolicy config options - Add AllowedUsers and BlockedUsers whitelist/blacklist - Add IsUserAllowed and ShouldProcessChannel methods - Integrate permission checks in message handling
- Fix pool.go to clean absolute paths with . or .. elements - Fix test code to replicate correct path resolution logic - Add tilde expansion support in expandPathFixed test helper
hrygo
force-pushed
the
feat/slack-permission-policy-v2
branch
from
ce6a3a9 to
5bc6dc5
Compare
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
1 participant
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.
Summary
Add permission policy support for Slack adapter, enabling fine-grained control over who can interact with the bot.
Changes
Context
Permission policy is essential for production deployments. This addresses the "权限策略(DM/Group)" gap identified in the comparison report. Now administrators can control:
Testing
Related