Add pre-publish checks #31
Merged
Conversation
This file contains 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
shawnbot
force-pushed
the
prepublish-checks
branch
from
c96969b to
8c31c06
Compare
|
hella cool 😍 |
aekong
approved these changes
Jul 15, 2021
shawnbot
force-pushed
the
prepublish-checks
branch
from
735cbcb to
e319bde
Compare
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.
This should help guard against accidentally deleting CSS bundles in the future. This build is an example of what it will look like if we (accidentally or intentionally) remove any of the CSS bundles that we have in there currently.
If we add a new bundle in the future, we should add it to the
dist/css/{...}.cssglob. If we remove a bundle in the future, we will have to remove it from the same glob to get the checks passing again.