-
Notifications
You must be signed in to change notification settings - Fork 69
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: update docstring to prevent jsx closing tag error #3328
fix: update docstring to prevent jsx closing tag error #3328
Conversation
✅ Deploy Preview for paragon-openedx ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
I created an issue for "Build Docs" failing silently #3329. I'll look into fixing that now. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3328 +/- ##
=======================================
Coverage 93.42% 93.42%
=======================================
Files 250 250
Lines 4515 4515
Branches 1017 1017
=======================================
Hits 4218 4218
Misses 294 294
Partials 3 3 ☔ View full report in Codecov by Sentry. |
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.
👍🏼
🎉 This PR is included in version 22.11.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Whoops! Thanks for the quick fix, @brian-smith-tcril :) |
🎉 This PR is included in version 23.0.0-alpha.7 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 22.11.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
The latest run of "Build Docs" (https://github.com/openedx/paragon/actions/runs/12241372269/job/34146296486) led to a silent failure. I haven't investigated why the failure was silent yet but the error hiding in there was:
I was able to reproduce the error locally by running
npm run build-docs
, and verified the error was gone with this change.