Skip to content
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

Update link in loplat.md #6734

Merged
merged 1 commit into from Jan 17, 2024
Merged

Conversation

hansonkim
Copy link
Contributor

Pull Request/Issue Resolution

Description of Change:

I have modified the link in the integration guide document (loplat.md). The update reflects the most recent information.

Closes #ISSUE_NUMBER_HERE

Is this change associated with a Braze feature/product release?

  • Yes (Insert Feature Release Date Here)
  • [ ✔️ ] No

Reviewers

@josh-mccrowell-braze
@bre-fitzgerald


✔️ Pull Request Checklist
  • [ ✔️ ] Check that you haven't removed any images (replacing an image with an updated one of the same name is fine), as this breaks the French site
  • [✔️ ] Check that all links work.
  • [ ✔️ ] Ensure you have completed our Contributors License Agreement.
  • [ ✔️ ] Tag @josh-mccrowell-braze and @bre-fitzgerald as a reviewer when your work is done and ready to be reviewed for merge. Are you an internal product manager? Reference the internal reviewing chart to tag the appropriate reviewer.
  • If the documentation involves a 1) paid SKU, 2) a third party, 3) SMS, 4) AI, or 5) privacy, ensure that Maria Maldonado on the Legal team has signed off.
  • Tag others as reviewers as necessary.
  • If you have modified any links, be sure to add redirects to assets > js > broken_redirect_list.js
⭐ Helpful Wiki Shortcuts
❗ ATTN: For PR Reviewers
  • Read our Reviewing a PR page for more on our reviewing suggestions.
  • Read our Previewing Documentation page to see how to check the deployment.
    • Preview all changes in the linked Vercel environment by clicking the preview link in the vercel-bot comment in your PR.
❗ ATTN: Internal Reviewing Chart
Work at Braze and not sure who to tag for review?
Before tagging @josh-mccrowell-braze or @bre-fitzgerald for a general review, reference the following chart to see if a specific product vertical/reviewer applies to your pull request.

Reviewer Product Vertical
@josh-mccrowell-braze Monolith Deployments
Quality Infrastructure
Platform Infrastructure
Datalake
SDKs
Currents
@bre-fitzgerald Intelligence
In-App Messages
Channels
FIX
@lydia-xie Ingestion
Core Objects
Core Messaging
Messaging Experience
Message Components
Email (Composition and Infrastructure) (tag @rachel-feinberg for Liquid use cases)
@rachel-feinberg Customer Lifecycle, Identity and Permissions
SMS
User Targeting
Reporting

I have modified the link in the integration guide document (loplat.md).
The update reflects the most recent information.
@cla-bot cla-bot bot added the cla-signed label Jan 15, 2024
@josh-mccrowell-braze
Copy link
Collaborator

Hi @hansonkim ! Thanks for helping keep our documentation up to date.

Is this PR ready to be merged?

@hansonkim
Copy link
Contributor Author

Hi @hansonkim ! Thanks for helping keep our documentation up to date.

Is this PR ready to be merged?

@josh-mccrowell-braze Yes, this PR is ready for merging.

@josh-mccrowell-braze josh-mccrowell-braze merged commit e496480 into braze-inc:develop Jan 17, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants