Fix branch builds for this repo

[yuvipanda]

Currently, if you push to a branch in this repo, Travis fails.

We should fix this!

[willingc]

@yuvipanda Do you think the latest addition of chartpress and the changes to .travis.yml fix this?

[consideRatio]

We currently end up with two builds on travis running, this is not the correct behavior i figure.

[consideRatio]

This is an example of an troublesome behavior, where we get two builds, one because we get a PR, and one because we added a branch.

Actionplan:

1. Ensure we only do one build in this case. For an example of this issue see the build for CHANGELOG.md contained duplicate instructions #877

[betatim]

Why not recommend against having private branches in this repository? We operate via PRs for all change so people have their own fork already and can do what they like there.

My preference for this is part "keeping the master repository tidy" and "only special people can make branches here and I don't like having special people".

[yuvipanda]

@betatim absolutely agree :)

[betatim]

-> close this issue? Or is there a GitHub setting we can/should use to enforce this?

[willingc]

I don't think that GitHub offers a straightforward way to prevent new branch creation. I'm going to close.