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

BD-3519: Remove duplicate use cases section from Creating a catalog article #8157

Merged
merged 1 commit into from
Sep 26, 2024

Conversation

lydia-xie
Copy link
Contributor

Why are you making this change? (required)

Remove duplicate use cases section from Creating a catalog article

Related PRs, issues, or features (optional)

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.

@cla-bot cla-bot bot added the cla-signed label Sep 26, 2024
Copy link

vercel bot commented Sep 26, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
braze-docs-ko ⬜️ Ignored (Inspect) Sep 26, 2024 5:55pm

Copy link
Contributor

@rachel-feinberg rachel-feinberg left a comment

Choose a reason for hiding this comment

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

Lgtm!

@rachel-feinberg rachel-feinberg merged commit e062ad0 into develop Sep 26, 2024
5 checks passed
@rachel-feinberg rachel-feinberg deleted the lx-bd-3519 branch September 26, 2024 18:01
@josh-mccrowell-braze
Copy link
Collaborator

@rachel-feinberg , @lydia-xie In this deployment, it looks like some of the image links are broken under "Using images." If we have time, it's probably worthwhile during reviews to give the vercel deployment a look to make sure everything looks shipshape.

@lydia-xie
Copy link
Contributor Author

@rachel-feinberg , @lydia-xie In this deployment, it looks like some of the image links are broken under "Using images." If we have time, it's probably worthwhile during reviews to give the vercel deployment a look to make sure everything looks shipshape.

Fixed in #8158

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.

3 participants