feat: add bot detection in data ingestion #3347
Open
+190
−10
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.
Changes proposed ✍️
Added bot detection logic to the
data-sink-worker
to automatically identify bot accounts during member creation. The detection system uses a three-tier approach:[bot]
notation, well-known bot services (e.g., dependabot, renovate, coderabbit), and other patterns.Bot flags provided by source integrations always take precedence over our detection logic, and suspected bots are explicitly flagged for LLM validation. Existing isBot values are preserved during member updates to ensure we do not overwrite integration-provided information.
Also,
blacklistedDomains
was converted from an array to a Set to improve lookup performance (O(1) vs O(n)).