-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
[6/6] build: common/static/css/xmodule -> xmodule/static/css #32291
[6/6] build: common/static/css/xmodule -> xmodule/static/css #32291
Conversation
bacfc5a
to
fcdb84b
Compare
c522ca3
to
47e142b
Compare
47e142b
to
fb63433
Compare
16185b0
to
315d125
Compare
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.
One small doc thing but then I think this is good to go.
eb2f650
to
81b5bf1
Compare
Now that all XModule SCSS is located in xmodule/static/sass, it would make sense to co-locate the CSS there as well. We also add a README to explain the purpose of this new folder. In the future, we will move xmodule/js and xmodule/assets into xmodule/static as well. Part of: openedx#32292
81b5bf1
to
46511d2
Compare
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. |
This reverts commit 5671dab.
Potential issue identified on studio.edx.org, prepping a revert here: #32526 |
Supporting information
This the final PR in a series:
The previous PR is:
The next series of PRs will be here:
Description
Now that all XModule SCSS is located in xmodule/static/sass,
it would make sense to co-locate the CSS there as well.
We also add a README to explain the purpose of this folder.
In the future, we will move xmodule/js and xmodule/assets
into xmodule/static.
Part of: #31624
Testing Instructions
Deadline
Medium urgency.