Skip to content

Adding use case on behalf of Braze #5379

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

Merged
merged 4 commits into from
Sep 21, 2023
Merged

Adding use case on behalf of Braze #5379

merged 4 commits into from
Sep 21, 2023

Conversation

tcgilbert
Copy link
Contributor

Proposed changes
adding this section on behalf of a use-case identified by Braze

Merge timing
asap

@tcgilbert tcgilbert requested a review from a team as a code owner September 19, 2023 19:44
@tcgilbert tcgilbert requested review from pwseg and removed request for a team September 19, 2023 19:45
@pwseg pwseg changed the title adding use case on behalf of braze Adding use case on behalf of braze Sep 21, 2023
@pwseg pwseg changed the title Adding use case on behalf of braze Adding use case on behalf of Braze Sep 21, 2023
@pwseg pwseg added the content-update updates to content that are not new features, includes grammar fixes, added notes label Sep 21, 2023
@pwseg pwseg merged commit b5662a4 into develop Sep 21, 2023
@pwseg pwseg deleted the thomas/cohorts branch September 21, 2023 17:00
@github-actions
Copy link
Contributor

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content-update updates to content that are not new features, includes grammar fixes, added notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants