“It’s not a good experience for a contributor to open a pull request and get eight requests for changes that could have been explained in a contributing guide.” - @lornajane (slightly paraphrased from memory)
Yes! 
@Sinjo @lornajane Which should have been pointed out, or even fixed, by the guide's recommended developer environment. Never make a contributor spend time fixing whitespace or sorting import statements, or anything else that tools can reliably do.
@kevin @Sinjo that’s fair if there’s a small set of tools that can be used. In general I prefer open source projects to allow contributors to use the tools they prefer. Some may not be able to afford official tools, others may be choosing tools that support accessibility needs, or simple preference. So my emphasis is on documenting the expected standards
@lornajane @Sinjo Agreed! The project's contribution requirements should never mandate non-FOSS tools, or even FOSS tools that are obscure or poorly supported. The project's maintainers need to take all of this into account when making their workflow choices.