-
Notifications
You must be signed in to change notification settings - Fork 0
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
Enable @wordpress/stylelint-config
#44
base: main
Are you sure you want to change the base?
Enable @wordpress/stylelint-config
#44
Conversation
Agree. Let's wait for upstream improvement. |
see also WordPress/gutenberg#65681 |
Thank you for linking that @Mouvedia |
WordPress/gutenberg#66272 has been merged. |
Tests for the WordPress Stylelint config are now working. |
@@ -14,6 +14,9 @@ on: | |||
stylelint-version-override: | |||
type: string | |||
description: The Stylelint version override | |||
working-directory-is-workspace: |
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.
npm workspaces often assume that npm install
and other commands are run from the project root.
See #39
Blocked on WordPress/gutenberg#59933
Gutenberg uses a bespoke setup to emulate workspaces.
I would like to avoid adding support for their custom setup and instead wait until they align with standard npm workspaces.