[Biopython-dev] Protecting master branch on GitHub?

[Christian Brueffer]

On 2015-09-04 11:02, Peter Cock wrote:
> Hi all,
>
> GitHub have rolled out some interesting new functionality:
> https://github.com/blog/2051-protected-branches-and-required-status-checks
>
> The ability to protect the main branch should prevent any accidental
> rewriting of the history (from a forced push), which would cause
> widespread inconvenience now we have so many forks. I'd like to
> enable this if no one objects.
>
> The second new feature would disable the web-GUI merge button
> until our TravisCI tests have passed. I usually do the merges at
> the command line anyway (sometimes rebasing, often to add a
> note to the NEWS and CONTRIB files), but again these seems like
> a sensible precaution? What do people think?
>

1. sounds great

2. sounds great in principle, however there are cases where Travis fails 
due to reasons other than broken code (e.g., timeouts etc).  Is there a 
way to say "I really really want this to go in despite Travis failing"?

Chris