Skip to content
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

Switch to WordPress-VIP-Go standards #1050

Closed
wants to merge 4 commits into from

Conversation

mjangda
Copy link
Member

@mjangda mjangda commented Dec 20, 2018

See #1032

@mjangda
Copy link
Member Author

mjangda commented Dec 20, 2018

Need to checkout the correct repo here: https://github.com/Automattic/vip-go-mu-plugins/blob/master/Makefile#L16

Since there are still many errors we need to work through.
@@ -13,20 +13,20 @@ phpunit:
phpdoc:
phpdoc run --no-interaction

phpcs:
initphpcs:
test -f /tmp/phpcs || curl -L https://squizlabs.github.io/PHP_CodeSniffer/phpcs.phar -o /tmp/phpcs && chmod +x /tmp/phpcs
test -d /tmp/wpcs || git clone -b master --depth 1 https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards.git /tmp/wpcs
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WPCS master and VIPCS master are not yet compatible.

The safest option for now, is to checkout the 1.2.1 tag of WPCS, and the 0.4.0 tag of VIPCS.

I'll make it clear in VIP when a release of VIPCS is compatible with WPCS master.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VIPCS 2.0 has been released, and it is compatible with WPCS 2.1+.

@mjangda
Copy link
Member Author

mjangda commented Apr 30, 2020

This was done.

@mjangda mjangda closed this Apr 30, 2020
@mjangda mjangda deleted the update/phpcs-WordPress-VIP-Go branch April 30, 2020 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants