cli: add whois command for cross-source person lookup - #382
Merged
Conversation
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.
Adds
pigeon whois <query>— resolves a name, handle, user ID, or email fragment against the synced identity files and prints one JSON line per person, with recent activity (last active, event count, top conversations) to tell similar names apart.--idprints a single bare Slack user ID for command substitution: exactly one match, or empty stdout with exit 2 and the candidates on stderr. The CLI send layer now rejects messages containing an empty mention before anything reaches the daemon or the review queue. Identity candidate search matches email fragments in all paths, and the root help documents the identity data layout and the whois lookup/send workflows. Two writer-side gaps found during design are filed in the bug backlog: WhatsApp identity lacks LID identifiers, and bots are indistinguishable from humans in people.jsonl.