Release 0.3.2: count exclude_leadgen default, CLI flag parity, cookbook - #18
Merged
Conversation
Six new scripts plus CLI one-liners covering the searches the API page shows: seed-domain TAM, icp_prompt search, phrase match with count first, CRM export enrichment, contacts at discovered companies, and an agent opening the account through signup(). README is now one table of script, purpose, and run command.
Regenerated against the platform spec; the SDK was sending true on every count and narrowing results the caller never filtered out.
discover and count gained variance, min-similarity, consensus, inclusion-query-id, language, social, subdomain, start-date, redirect, exclude-leadgen and the auto-* toggles; contacts search, count, and discover gained the full filter set; match gained per-column flags for file mode and min-match-confidence; append and segment take query-id; extract accepts --domain. test_sdk_parity.py walks every build_request site with ast and fails on any unforwarded field, so a new SDK field cannot ship without its flag. icp_text stays out on purpose (dropped in 0.1.1 for icp_prompt) and dict-typed fields remain --param only; both are allowlisted by name.
yudelevi
changed the title
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
The count command reused the discover help text, which says the exclusion is on by default. CountParams now defaults it to false.
Contributor
Author
|
@greptileai review |
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.
CountParams.exclude_leadgendefaults toFalse, matching the platform/counthotfix (platform MR !813).examples/cookbook of runnable GTM recipes.Greptile Summary
The PR releases SDK and CLI version 0.3.2, aligns the count lead-generation exclusion default with the platform, expands CLI request-field parity, and adds runnable cookbook examples.
CountParams.exclude_leadgento default toFalse.Confidence Score: 5/5
The PR appears safe to merge.
No blocking failure remains.
Important Files Changed
CountParams.exclude_leadgennow defaults to false whileDiscoverParamsremains true, matching the intended endpoint-specific behavior.Reviews (2): Last reviewed commit: "cli: count --exclude-leadgen help says o..." | Re-trigger Greptile