Enable gh-pages testing if explicitly added to .travis.yml

[sarahhodne]

This was requested in travis-ci/travis-ci#476.

If you add this to your .travis.yml file, the gh-pages branch will be tested by Travis.

branches:
  only:
    - gh-pages

See the pull request mentioned above for rationale for this.

[joshk]

seems good to me 👍

[svenfuchs]

do we want people to whitelist every branch just so they can test their gh-pages?

[joshk]

I saw it that if people wanted to test their GH pages branch then they wouldn't be testing others, I could be wrong in this assumption, maybe:

branches:
  gh_pages: true

?

---

Sent from my Sega Master System

On 13/12/2012, at 12:53 PM, Sven Fuchs notifications@github.com wrote:

do we want people to whitelist every branch just so they can test their gh-pages?

—
Reply to this email directly or view it on GitHub.

[svenfuchs]

yeah, that makes sense to me. i guess we should allow both.

[sarahhodne]

branches:
  gh_pages: true

seems fine with me. Should be pretty trivial to implement too. Do you want a PR?

[joshk]

Yes pretty please :)

---

Sent from my Sega Master System

On 13/12/2012, at 5:49 PM, Henrik Hodne notifications@github.com wrote:

branches:
gh_pages: true
seems fine with me. Should be pretty trivial to implement too. Do you want a PR?

—
Reply to this email directly or view it on GitHub.

[sarahhodne]

It is documented here.

 Note that the gh-pages branch will not be built unless you add it to the whitelist (branches.only).

We're working on making the docs better, though, so we'll keep this in mind when reworking this part of the docs.

--Henrik

On June 15, 2013 at 4:26:44 AM, Pavel Puchkin (notifications@github.com) wrote:
This should be documented. I spent an hour trying to understand what's wrong with my configuration! :)
—
Reply to this email directly or view it on GitHub.

[kylekatarnls]

Hi, but force to use branch.only is a big constraint. How to run tests on all branches and future branches including gh-pages?