MediaWiki-Codesniffer (packagist, Gerrit) has improved considerably over the last few months and it's probably a good idea to make core pass the codesniffer tests.
- Generic.CodeAnalysis.ForLoopWithTestFunctionCall.NotAllowed
- Generic.Files.EndFileNewline.NotFound
- Generic.Files.LineLength
- Generic.WhiteSpace.DisallowSpaceIndent.SpacesUsed
- MediaWiki.NamingConventions.PrefixedGlobalFunctions.wfPrefix
- MediaWiki.VariableAnalysis.UnusedGlobalVariables
- MediaWiki.WhiteSpace.SpaceAfterControlStructure.Incorrect
- MediaWiki.WhiteSpace.SpaceyParenthesis.SingleSpaceAfterOpenParenthesis
- MediaWiki.WhiteSpace.SpaceyParenthesis.SingleSpaceBeforeCloseParenthesis
- PSR2.Methods.MethodDeclaration.AbstractAfterVisibility
- PSR2.Methods.MethodDeclaration.StaticBeforeVisibility
- PSR2.Methods.MethodDeclaration.Underscore
- PSR2.Namespaces.NamespaceDeclaration.BlankLineAfter
- Squiz.Classes.ValidClassName.NotCamelCaps
- Squiz.WhiteSpace.ScopeClosingBrace.Indent
- Squiz.WhiteSpace.SemicolonSpacing.Incorrect
- Squiz.WhiteSpace.SuperfluousWhitespace.EmptyLines
After this, T102598 could happen and we could have mediawiki-codesniffer running as a voting jenkins job against master.
The output of mediawiki codesniffer running against core (at 3247aa82027) can be found at P789.
The output against core (at 03c1d480a7d) and ignoring languages/messages and languages/classes can be found at P815.
You can try this out yourself by running:
phpcs --standard=vendor/mediawiki/mediawiki-codesniffer/MediaWiki --extensions=php,php5,inc --ignore=vendor,extensions -p .