-
Notifications
You must be signed in to change notification settings - Fork 14
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
DataGrail Partnership Documentation #3900
Merged
Merged
Conversation
This file contains 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
KellieHawks
added
the
Braze Partnerships
Integration docs submitted to the braze-docs repo by Braze partners.
label
Aug 9, 2022
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
KellieHawks
changed the title
DataGrail Partnership Docs
DataGrail Partnership Documentation
Aug 9, 2022
bre-fitzgerald
requested changes
Aug 12, 2022
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.
looks good! just two small things for your review :)
_docs/_partners/data_and_infrastructure_agility/data_privacy/datagrail.md
Outdated
Show resolved
Hide resolved
_docs/_partners/data_and_infrastructure_agility/data_privacy/datagrail.md
Outdated
Show resolved
Hide resolved
…atagrail.md Co-authored-by: Bre Fitzgerald <82903296+bre-fitzgerald@users.noreply.github.com>
bre-fitzgerald
approved these changes
Aug 12, 2022
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.
lgtm!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Pull Request/Issue Resolution
Description of Change:
Closes #ISSUE_NUMBER_HERE
Is this change associated with a Braze feature/product release?
✔️ Pull Request Checklist
assets
>js
>broken_redirect_list.js
⭐ Helpful Wiki Shortcuts
❗ ATTN: For PR Reviewers
❗ ATTN: Internal Reviewing Chart
Work at Braze and not sure who to tag for review?
Before tagging @timothy-kim or @KellieHawks for a general review, reference the following chart to see if a specific product vertical/reviewer applies to your pull request.
Platform Infrastructure
Quality Infrastructure
Product Partnerships
SDKs
SMS
FIX
Intelligence
Reporting
SMB
Ingestion
Messaging