I feel a bit of responsibility for sending you down this road... so I figure I should post a few tips about Travis CI. I apologise if you know all of this already, but maybe someone else that comes across it wont.
Travis is equal parts awesome and awful. The awful is partly the docs which can be a bit hard to work with, but mainly the slowness of the edit-build-test cycle. A typical session for me would usually go...
10 FIX .travis.yml
20 git commit -va --amend
30 git push -f
40 WAIT FOR TRAVIS EMAIL...
50 GOTO 10
This process seriously tests my sanity. Get ready for a lot of sword fighting practise.
(Make sure you use their container based build environment, it's a lot lot faster.)
The other really really critical thing is:
If you ever accidentally push secrets (e.g. keys or auth tokens) to GitHub, revoke them immediately!
There are bots that scan for that kind of thing, it doesn't matter how quickly you force push them out of existence, you need to assume them to be compromised. There are horror stories out there about AWS keys...