Skip to content

Conversation

EvanYoung-SP
Copy link
Contributor

@EvanYoung-SP EvanYoung-SP commented Dec 9, 2021

this is for testing purposes (DO NOT MERGE)

// Give your PR a recognizable title. For example: "FE-123: Add new prop to component" or "Resolve Issue #123: Fix bug in component" // Your PR title will be visible in changelogs

What Changed

// What changes does this PR propose? // Provide screenshots or screen recordings for any visual changes.

PR Checklist

  • Give your pull request a meaningful name.
  • Use lowercase filenames.
  • Pull request approval from the FE team or content experts that isn't the content creator.
  • Check that your article looks correct in the preview here or in a Netlify deploy preview.
  • Check the links in your article.
  • Check the images in your article (if there are any)
  • Check to make sure you are using markdown appropriately as outlined in examples/article.md in the root of the project directory and on the momentum doc's preface article
  • Check to make sure the Copy and Tone Guidelines are followed.

this is for testing purposes (DO NOT MERGE)
@EvanYoung-SP EvanYoung-SP requested a review from jonambas December 9, 2021 17:11
@netlify
Copy link

netlify bot commented Dec 9, 2021

✔️ Deploy Preview for support-docs ready!

🔨 Explore the source changes: 2540e20

🔍 Inspect the deploy log: https://app.netlify.com/sites/support-docs/deploys/61b238d61f93c7000745503a

😎 Browse the preview: https://deploy-preview-632--support-docs.netlify.app

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant