Support optional use of Github secrets to workaround rate limits

[palfrey]

This would fix #859 (429 errors from Github) but I don't have enough permissions to add a new secret value to Travis.

@luciusmagn Any thoughts? Do you have enough access for this?

[palfrey]

@kud1ing Do you still have enough access to add a secret? Relatedly, I don't appear to be able to restart Travis builds anymore which I used to be able to :(

[kud1ing]

Hi, no i am sorry. This is bound to the organization, which i've left.

[palfrey]

@Manishearth Can you help here?

[Manishearth]

Can't secrets be added to the travis.yml?

I'm uncomfortable with adding my own account secrets and don't have time to make a dummy account.

[palfrey]

I'm ok with adding my own secrets to the travis.yml, but only if they're encrypted with the standard Travis encryption stuff. I can't do that however as I don't have enough access on travis, probably because I don't have enough access on this repository. If that can be fixed, I can fix the rest of things myself.

[badboy]

We should be able to make @palfrey an admin on this repo. @Manishearth, you're good with that?

[palfrey]

@badboy @Manishearth Any further thoughts on this?

[Manishearth]

Yeah, this has been in my queue, i just have a ton of notifications to deal with.

You've been maintaining this pretty well, I'm okay with granting admin access. Please use it responsibly 😄

[palfrey]

Cool, thanks. I've added the secrets now (in the Travis UI, not the .travis.yml)