Continuing the discussion from How to view detailed travis flake8 errors?:
I wonder if we could adjust the way Travis is configured for our repos.
I too want the highest level of code quality, but it is a problem when Travis prevents merging a PR because code-analysis thinks that logic in code I have not touched nor changed is too complicated.
So far I have modified code in files I did not want to change, only because flake8 was complaining about lines being over 79 chars or an extra space being "needed" after a comment character.
But it is not right that I should be forced to modify logic in another file (again a file I did not touch in my PR). This is a big problem because:
- I have to take extra time to modify code that isn't broken and that has nothing to do with my PR
- I risk breaking that code when I have to redo its logic to satisfy this measure of complexity: https://en.wikipedia.org/wiki/Cyclomatic_complexity
The end result is that my PR will not get merged, my contribution will not be accepted, and I will have wasted a lot of time.
- configure Travis to warn, but not block merging of PRs
- configure Travis to report the code-analysis errors, rather than making each of us run it locally just to find out the details of the flake8 errors it found
- configure Travis to complain (or possibly block) merging of code that the PR modified, ignoring unmodified code
- configure Travis in a "strict" way only on the github.com/plone organization, but not so much on the collective?