-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Google Threat Intelligence] Private url scanning #38457
[Google Threat Intelligence] Private url scanning #38457
Conversation
Thank you for your contribution. Your generosity and caring are unrivaled! Make sure to register your contribution by filling the Contribution Registration form, so our content wizard @talzich will know the proposed changes are ready to be reviewed. |
Hi @pabloperezj, thanks for contributing to the XSOAR marketplace. To receive credit for your generous contribution please follow this link. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @pabloperezj, and thank you for your contribution!
To move forward with our review the CLA needs to be signed 😃
Done. Thanks! @talzich |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @pabloperezj, I've reviewed your contribution and overall things look great!
A few comments to make it perfect :)
Also, notice the pre-commit failure and let me know if you need any help resolving that.
Cheers,
Tal
...s/GoogleThreatIntelligence/Integrations/GoogleThreatIntelligence/GoogleThreatIntelligence.py
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the data in that file (urls, ids, twitter handles etc.) OK for publish?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it is OK!
Hi @talzich, thank you for your review :) I had some problems with the pre-commit, it would be great if you could help me :) |
Sure! Sent you some instructions and examples via Slack |
For the Reviewer: Trigger build request has been accepted for this contribution PR. |
For the Reviewer: Successfully created a pipeline in GitLab with url: https://gitlab.xdr.pan.local/xdr/cortex-content/content/-/pipelines/2425571 |
f4259b2
into
demisto:contrib/VirusTotal_feat/gti-private-url-scanning
Thank you for your contribution. Your external PR has been merged and the changes are now included in an internal PR for further review. The internal PR will be merged to the master branch within 3 business days. |
* feat(GTI): Private URL scanning * Add tests * Add tests * Update yml * Generate docs * Update release note * Fix * Fix pre-commit * Update docker image * Fix * Fix Co-authored-by: Pablo Pérez <[email protected]>
Contributing to Cortex XSOAR Content
Make sure to register your contribution by filling the contribution registration form
The Pull Request will be reviewed only after the contribution registration form is filled.
Status
Related Issues
fixes: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.
Must have