Ryan Hiebert

As far as I can tell, the new GraphQL API for github (v4) does not (yet) have a way to add statuses to commits. It seems that will require v3...

I'd really appreciate some feedback on this question. I've been playing around with the GitHub API, and working up what it would take to get it working on Travis. I've...

You're right, there's a lot in common with codecov for this purpose. I'm not sure how codecov validates the uploads it gets from Travis for public repositories (which don't require...

I'm waiting on response from codecov, but I suspect that they actually don't authenticate _any_ coverage uploads. They do have uuid-like repository tokens for private repos, but I think that's...

A possibility for the 3rd party service would be to allow envs to be reported by identification only (by build id, perhaps), but limit it in two ways: 1. Only...

For some reason I had thought that the `python: 3.6` also wasn't working, so I'm glad to find out it is. Are you finding anything in your implementation that needs...

Oh that's interesting. Doing that seems like a reasonable idea. I'm not immediately sure how reasonable an implementation would be.

This is expected behavior. Declared configuration is always matched exactly, so having "3.8-dev" in the Travis configuration won't match "3.8" in the tox-travis config. Instead, it falls back to the...

OK, that's a more reasonable thought, then, if it only attempts to work with a single job. Let me share another thought with you, and see if it affects your...

You've convinced me that attempting to warn using `TRAVIS_JOB_NUMBER` is a bad idea. I'll go even further, though and say that given the complexity, attempting to warn at all when...