search

w3c / testtwf-website-src

Sources for http://testthewebforward.org/
10 stars 17 forks source link

Make travis use correct branch, not always master #6

Closed sideshowbarker closed 9 years ago

sideshowbarker commented 9 years ago

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

tagawa commented 9 years ago

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

sideshowbarker commented 9 years ago

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 commented 9 years ago

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 commented 9 years ago

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 commented 9 years ago

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