Make travis use correct branch, not always master

[sideshowbarker]

Without this change, travis fails with error: pathspec 'master' did not match any file(s) known to git.

[tagawa]

My git fu is not strong enough to merge this - any other takers?

[sideshowbarker]

My git fu is not strong enough to merge this - any other takers?

@jgraham wrote that rakefile and the travis setup, so he probably ought to doublecheck this to make sure it's not going to break anything.

[jgraham]

I don't understand why this is needed. Running travis on !master seems bad because it will try to push that other branch into production.

[sideshowbarker]

I don't understand why this is needed. Running travis on !master seems bad because it will try to push that other branch into production.

OK, I didn't know that the travis setup was actually always pushing changes to production.

Given that, I've now disabled the "Build pull requests" option at https://travis-ci.org/w3c/testtwf-website-src/settings

We want that disabled, right?

[jgraham]

Yeah, I thought that was already disabled, but that might have been my test setup.