Ignoring the fact that I think the assertion of this PR is tenuous at best, I would definitely want to see a test that sets the file_header value in .editorconfig to something, to ensure that does not move, otherwise this refactoring would just immediately trigger a diagnostic. Also I think the best thing would be not moving the trivia if file_header has a value at all, rather than trying to be smart about it, as I doubt its worth trying to put in the smarts to handle the file header plus some other trivia and split them up etc.

Closing this PR. I am not familiar with .editorconfig options and the way I can access them inside refactoring provider, so I feel I cannot implement the fix properly.

@DoctorKrolic are you ok if I push to your branch?

@CyrusNajmabadi Here 100% ok. I spent about half an hour trying to figure out how to get code style options and didn't find a way in the end. It would be interesting for me to know the answer)

/azp run