Skip to content

feat: enforce virtual-collaborators allow-list in runtime flow#2

Merged
heoh merged 1 commit intomainfrom
gh-1
Feb 24, 2026
Merged

feat: enforce virtual-collaborators allow-list in runtime flow#2
heoh merged 1 commit intomainfrom
gh-1

Conversation

@heoh
Copy link
Owner

@heoh heoh commented Feb 24, 2026

Summary

Fixes an issue where virtual-collaborators was parsed but not enforced at runtime.
When configured, only allowed VC names are used for parsing, tagging, and notifications.

Changes

  • context.ts: normalize allow-list input (trim, remove empty values, dedupe)
  • tag-util.ts: apply allow-list filtering to header/mention//assign and watcher resolution
  • handlers: pass allow-list into watcher calculation
  • tests: add allow-list + backward compatibility coverage

Verification

  • npm test -- --runInBand
  • npm run lint
  • npm run build

@heoh heoh added the enhancement New feature or request label Feb 24, 2026
@heoh heoh merged commit ccd19d4 into main Feb 24, 2026
@heoh heoh deleted the gh-1 branch February 24, 2026 13:58
@heoh heoh linked an issue Feb 24, 2026 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

virtual-collaborators is not enforced in runtime logic

1 participant