Seemed like this should be scriptable though – turns out it is! Edit that script to include your GitHub login details, and Travis-CI details, save it as
travis-status somewhere in your $PATH,
chmod +x travis-status and you’re ready to go!
travis-status in a project’s root directory (and I’m assuming the project’s root directory has the same name as the repository’s slug) with no parameters will print out a list of all event hooks for the project (not just Travis ones). Running it and passing “1” or “0” as the parameter will enable or disable Travis for the project.