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

Notify Partner docs #8365

Merged
merged 3 commits into from
Nov 25, 2024
Merged

Notify Partner docs #8365

merged 3 commits into from
Nov 25, 2024

Conversation

alex-braze
Copy link
Collaborator

The partner docs submitted by Notify.

Why are you making this change? (required)

Your reason here...

Related PRs, issues, or features (optional)

  • N/A

Feature release date (optional)

  • N/A

Contributor checklist

  • I confirm that my PR meets the following:
    • I signed the Contribution License Agreement (CLA).
    • My style and voice follows the Braze Style Guide.
    • My content contains correct spelling and grammar.
    • All links are working correctly.
    • If I renamed or moved a file or directory, I set up URL redirects for each file.
    • If I updated or replaced an image, I did not remove the original image file from the repository. (For more information, see Updating an image).
    • If my PR is related to a paid SKU, third party, SMS, AI, or privacy, I have received written approval from Braze Legal.

Submitting for review

If your PR meets the above requirements, select Ready for review, then add a reviewer:

  • Non-Braze contributors: Add braze-inc/docs-team as the reviewer.
  • Braze employees: Have any relevant subject matter experts (like engineers or product managers) review your work first, then add the tech writer assigned to your specific vertical. If you're not sure which tech writer to add, you can add braze-inc/docs-team instead.

Thanks for contributing! We look forward to reading your work.

The partner docs submitted by Notify.
@cla-bot cla-bot bot added the cla-signed label Nov 4, 2024
@josh-mccrowell-braze josh-mccrowell-braze added Braze Partnerships Integration docs submitted to the braze-docs repo by Braze partners. status: in progress Work in progress. labels Nov 5, 2024
Copy link

vercel bot commented Nov 13, 2024

@lydia-xie is attempting to deploy a commit to the Braze team on Vercel, but is not a member of this team. To resolve this issue, you can:

  • Make your repository public. Collaboration is free for open source and public repositories.
  • Add @lydia-xie as a member. A Pro subscription is required to access Vercel's collaborative features.
    • If you're the owner of the team, click here and add @lydia-xie as a member.
    • If you're the user who initiated this build request, click here to request access.
    • If you're already a member of the Braze team, make sure that your Vercel account is connected to your GitHub account.

To read more about collaboration on Vercel, click here.

Copy link
Collaborator Author

@alex-braze alex-braze left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a couple comments otherwise this looks gtm!

@lydia-xie lydia-xie removed the status: in progress Work in progress. label Nov 14, 2024
@lydia-xie
Copy link
Contributor

@alex-braze thanks for the feedback, just made the edits! Let me know when this PR is ready to be merged 🫡 🚀

Copy link
Collaborator Author

@alex-braze alex-braze left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks gtm!

@lydia-xie lydia-xie removed the request for review from internetisaiah November 25, 2024 22:37
@lydia-xie lydia-xie merged commit c6759a8 into develop Nov 25, 2024
1 of 4 checks passed
@lydia-xie lydia-xie deleted the alex-braze-notify branch November 25, 2024 22:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Braze Partnerships Integration docs submitted to the braze-docs repo by Braze partners. cla-signed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants