Stephan Bönnemann-Walenta

But, I'm thinking, we're generating a github token already, why don't we just that one for both npme and travis? I liked the idea for generating a new token for...

Combining it with the findings of this issue: https://github.com/semantic-release/semantic-release/pull/53 this is how it would work: If the pkg.name contains a scope we call `conf.get('@'+scopeName+'/registry')`. If that returns a registry we...

I'm pretty sure it is. Can you think of any case where this would return a non enterprise registry?

Okay I see, because it's actually just a GitHub token, npm doesn't do anything to the token on logout. I'm fine with your plan then :+1: One caveat `conf.get(registry +...

Alright here you go for the nerf-darts: https://github.com/boennemann/nerf-dart

Hey @apowers313, Sorry for the late reply, I didn't really have internet the past week. First of all thanks so much for this, this is very valuable feedback and a...

I love the idea :+1:

Hey @linclark (: First of all sorry for this taking so long. I could reproduce your error and will give you detailed instructions on how to fix that now (I...

The identification and log comes from the `travis enable` command. While doing #8 we can fix this. This bothers me as well ;)

Is this something that appeared during development, or during "real-world" use?