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

Correct spelling #18442

Closed
wants to merge 2 commits into from
Closed

Conversation

hugovk
Copy link
Contributor

@hugovk hugovk commented Oct 7, 2018

Description

Correct spelling mistakes.

Manual testing scenarios

  1. Check tests pass with no regressions

Contribution checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • [n/a] All new or changed code is covered with unit/integration tests (if applicable)
  • [Pending] All automated tests passed successfully (all builds on Travis CI are green)

@miguelbalparda
Copy link
Contributor

Hi @hugovk! Can you please check the failing tests? Thank you!

@miguelbalparda miguelbalparda self-assigned this Oct 8, 2018
@hugovk
Copy link
Contributor Author

hugovk commented Oct 8, 2018

@miguelbalparda Will do. That's strange they didn't fail on my fork:

https://travis-ci.org/hugovk/magento2/builds/438317027

There's probably also some bug in the build scripts which meant it didn't fail when it should, compare:

https://travis-ci.org/magento/magento2/jobs/438331102#L948
https://travis-ci.org/hugovk/magento2/jobs/438317030#L938

@orlangur
Copy link
Contributor

@hugovk, "Fix Code Sniffer using PHPCBF" - please avoid such changes or at least don't use rules not used in Magento, like PHPDoc alignment.

@hugovk
Copy link
Contributor Author

hugovk commented Nov 5, 2018

Closing this, I didn't get time to tidy it up and it's since got to merge conflict hell, but at least some of it was merged in another PR.

@hugovk hugovk closed this Nov 5, 2018
@hugovk hugovk deleted the 2.3-develop-fix-spelling branch November 5, 2018 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment