fix: Updates task in topics sync API #36853
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AhtishamShahid
force-pushed
the
ahtisham/fix_topics_sync_api
branch
from
c3cb8c9 to
3827c4d
Compare
muhammadadeeltajamul
approved these changes
Jun 4, 2025
fix: Updates task in topics sync API fix: Updates task in topics sync API
AhtishamShahid
force-pushed
the
ahtisham/fix_topics_sync_api
branch
from
3827c4d to
c59a9ad
Compare
Contributor
|
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
Contributor
|
2U Release Notice: This PR has been deployed to the edX production environment. |
marlonkeating
pushed a commit
that referenced
this pull request
Jul 15, 2025
fix: Updates task in topics sync API
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updated task to update_discussions_settings_from_course_task because it uses a slightly different mechanism for creating topics . The existing implementation is causing unexpected results.