Timo Rothenpieler

Results 55 comments of Timo Rothenpieler

My understanding of it is that if you are using the Github Actions natively provided GITHUB_TOKEN secret or ${{ github.token }}, you use the github service. Coveralls then works some...

Are there really repositories that supply a variable called GITHUB_TOKEN, and put the Coveralls Token in there? Pretty sure in my original PR, bringing up proper support for GitHub Actions,...

I still think it's odd to put anything but the GITHUB_TOKEN into the env var called GITHUB_TOKEN. Putting the coveralls provided token in there seems very confusing for both users...

In my original PR adding support for the actual 'github' service type, I also introduced use of the env variable called GITHUB_TOKEN: https://github.com/TheKevJames/coveralls-python/commit/f597109b62fadaf900af79d4f08a7debee5229e2 Before that, I don't think it was...

I think I have the exact same problem. https://github.com/OGGM/oggm/pull/1033 All the parts of the parallel build fail the build, despite the final result being successful. How does one tell it...

When I tried that, it lead to coveralls not associating any but one of the partial jobs with my code, losing large chunks of the coverity results.

So coveralls must have changed something on their end then. Changing it like that will also break finishing the parallel job with the official coveralls action. Cause they set(at https://github.com/coverallsapp/github-action/blob/master/src/run.ts#L47)...

![out](https://user-images.githubusercontent.com/16896306/85434662-acf1e300-b586-11ea-9f68-2a730f6e5e8f.png) This is the result of running against netcdf-c 4.7.3 with https://github.com/Unidata/netcdf-c/commit/3bcdb5fbf11af85e63f7916768b13b1f7d02c860 backported. I could not use 4.7.4 because it made a major API and ABI change it seems, changing...

I have come up with this in my custom config to achieve pretty much what I wanted by now: ``` c.DockerSpawner.mounts.append({ 'source': 'jupyter-storage-{username}', 'target': '/home/jovyan', 'type': 'volume', 'driver_config': { 'Options':...

Since this seems like a case a lot of people would want, it might be worth it to document that option somewhere, so someone else does not need to go...