Update travis-ci config

[ixti]

No description provided.

[coveralls]

Coverage remained the same at 100.0% when pulling ac80262 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 847b847 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 847b847 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 847b847 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 847b847 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 847b847 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 847b847 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 1bffef2 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling fd557ac on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling fd557ac on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling fd557ac on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling fd557ac on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling fd557ac on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling fd557ac on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling fd557ac on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling fd557ac on improve/testing into a2e5e06 on master.

[coveralls]

Coverage decreased (-0.9%) to 99.13% when pulling 5b5206f on improve/testing into a2e5e06 on master.

[coveralls]

Coverage decreased (-0.9%) to 99.13% when pulling 5b5206f on improve/testing into a2e5e06 on master.

[coveralls]

Coverage decreased (-0.9%) to 99.13% when pulling 5b5206f on improve/testing into a2e5e06 on master.

[coveralls]

Coverage decreased (-0.9%) to 99.13% when pulling 5b5206f on improve/testing into a2e5e06 on master.

[coveralls]

Coverage decreased (-0.9%) to 99.13% when pulling 5b5206f on improve/testing into a2e5e06 on master.

[coveralls]

Coverage decreased (-0.9%) to 99.13% when pulling 5b5206f on improve/testing into a2e5e06 on master.

[coveralls]

Coverage decreased (-0.9%) to 99.13% when pulling 5b5206f on improve/testing into a2e5e06 on master.

[coveralls]

Coverage decreased (-0.9%) to 99.13% when pulling 5b5206f on improve/testing into a2e5e06 on master.

[abotalov]

Could you authorize with AppVeyor, add this project there and run a build with this PR?
I had some issue on Windows (rubocop/rubocop#3401, rubocop/rubocop#3800) when I tried to update Rubocop to 0.47.0

[coveralls]

Coverage remained the same at 100.0% when pulling 3ba16a7 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 3ba16a7 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 3ba16a7 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 3ba16a7 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 3ba16a7 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling 3ba16a7 on improve/testing into a2e5e06 on master.

[ixti]

@abotalov sure. and we need to make coveralls be less noizy

[ixti]

@abotalov added - although i must admit that appveyor's integration kinda terrible IMO

[coveralls]

Coverage remained the same at 100.0% when pulling e165f41 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling e165f41 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling e165f41 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling e165f41 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling e165f41 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling e165f41 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling e165f41 on improve/testing into a2e5e06 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling e165f41 on improve/testing into a2e5e06 on master.

[ixti]

@abotalov is there a way to make enforce LF stay LF on Windows? I don't have any windows machines so i can't play around myself.

[abotalov]

@ixti You can revert commit a7565fc

This will fix AppVeyor but it will not make Rubocop passed if git config core.autocrlf = true which is a recommended setting on Windows as said in Github docs and Git Book.

I think it would be better to disable Style/EndOfLine cop as it doesn't work properly (rubocop/rubocop#3401, rubocop/rubocop#3800) and disabling will make default rake task work for others on Windows.

[ixti]

@abotalov I tend to either avoid rubocop on windows or removing that git config setting on appveyor. So far second thing seems more simple to me. Developers on windows can disable Style/EndOfLine on rubocop while developing.