Move content_tagging django app so that CMS-only tests run - #33259
Conversation
|
Thanks for the pull request, @rpenido! Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. Please let us know once your PR is ready for our review and all tests are green. |
2974693 to
f24910c
Compare
This reverts commit d0504a9ae087d815930b440ce534a2b961836239.
f8e691d to
5099629
Compare
|
Hi @bradenmacdonald! This is ready for your review! |
|
@rpenido 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
|
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
|
2U Release Notice: This PR has been deployed to the edX production environment. |
1 similar comment
|
2U Release Notice: This PR has been deployed to the edX production environment. |
|
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
|
2U Release Notice: This PR has been deployed to the edX production environment. |
1 similar comment
|
2U Release Notice: This PR has been deployed to the edX production environment. |
Description
This PR moves the content_tagging from
openedx/features/toopenedx/core/djangoapps/content_taggingthe tagging REST API for creating/updating object tags in Courses and XBlocks.Supporting Information
Testing instructions
openedx-4shard.Private ref: FAL-3500