introduce WPCS #2
Open
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
stklcode
force-pushed
the
wpcs
branch
3 times, most recently
from
89fc532 to
bdef8ad
Compare
stklcode
force-pushed
the
wpcs
branch
2 times, most recently
from
082cfa3 to
83c60ae
Compare
Member
|
Any reason why this is not merged? @krafit |
Verify compliance to coding standards in GH action. The necessary environment files should not be deployed, so the deployment action explicitly uses the .distignore file to exclude them.
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.
First a small change to the deployment action to not deploy any branches but main (obviously worked 😌) and second two commits with minor adjustments to match WordPresss Coding Standards.
Finally, the phpcs.xml, .stylelintrc.json and any package manger definitions are being added to a .distignore file, so they are excluded from deployment.