Closed strk closed 4 years ago
The EditorConfig action from marketplace is too expensive, BUILDS a docker to run that simple check, really not that ideal. Better get back to simple checking... (see https://github.com/linz/gazetteer/runs/536081065)
Ive made a number of changes in branch 2to3 that I'm guessing will conflict. I will run these through black to tidy up white spaces.
If this wasn't too much work I think it would be easier to close this and I will clean the branch that I already have many changes to the same files.
Big improvement here is the CI testing for blanks not to come back, if you enable that test in your branch and ensure is passes, I'm happy to close this. But note I did this because any file I'd touch would otherwise be changed to match editorconfig recommendations and this means my changes would be a mix of style and functional changes. The goal here was to keep those commits separated.
Big improvement here is the CI testing for blanks not to come back, if you enable that test in your branch and ensure is passes, I'm happy to close this. But note I did this because any file I'd touch would otherwise be changed to match editorconfig recommendations and this means my changes would be a mix of style and functional changes. The goal here was to keep those commits separated.
This would have been best practice. Unfortunately I have made many functional code changes to the same files. I will added the CI into my branch and get this merged ASAP.
@SPlanzer did you port the workflow in your PR yet ? Let me know if so, then we can close this one
@SPlanzer did you port the workflow in your PR yet ? Let me know if so, then we can close this one
I have added it to .github/workflows/push.yml but commented it out as there needs to be a piece of work to solve formatting issues. This will be the next task.
Based on this I think we can close this
Ok, closing, thanks
Respects editorconfig