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
fix(OMA): fixing OMA docs still in file system #17105
Conversation
Hi @jeff-colucci 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). |
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jeff-colucci this looks good to me!
The merge conflict is a bit of a pain, it's just confused since your PR deletes those files but they've been updated since you created this branch. Just make sure you don't "fix" the conflict the wrong way and keep the translated files on accident!
Merging after prior approval (I only merged develop in as the change since the review) |
No description provided.