GDS 2.x update and trimming #17
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
jexp
approved these changes
Apr 13, 2022
|
Yes, please.
…On Wed, Apr 13, 2022, 5:24 AM Michael Hunger ***@***.***> wrote:
***@***.**** approved this pull request.
Looks good, thanks a lot.
Shall I push it to s3?
—
Reply to this email directly, view it on GitHub
<#17 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOX3JD4JAFBGL6ZGP2IA5KDVE2OD7ANCNFSM5TH4JQUQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR updates the fraud detection browser guide to be compliant with GDS 2.x. In addition, Field has pointed out that the original guide was too much and more of a tutorial with exercises than a browser guide. As such, @pdathar created this new, trimmed down browser guide using the PaySim dataset.
I have created this PR and, since there are many changes, figured that there should be review of it by multiple stakeholders. However, this is Phani's work so I leave it to him to address the changes.
If there are stakeholders who are not already listed on this PR, please feel free to add them!
/cc @pdathar for addressing feedback and moving this PR forward
/cc @zach-blumenfeld @jexp @voutilad for review
/cc @AliciaFrame @moxious for visibiliy, comment, and/or review