Giters

purescript / purescript-either

Values with two possibilities

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Travis publish to Pursuit fails with dirty working tree

kritzcreek opened this issue · comments

commented 
$ test $TRAVIS_TAG && echo $GITHUB_TOKEN | pulp login && echo y | pulp publish --no-push
Please obtain a GitHub personal access token at:
  https://github.com/settings/tokens/new
No scopes are required, so don't check any of the boxes.

After you've done that, paste it in here: Successfully authenticated as garyb.
* ERROR: Your git working tree is dirty. Please commit or stash your changes first.

https://s3.amazonaws.com/archive.travis-ci.org/jobs/246280467/log.txt?X-Amz-Expires=30&X-Amz-Date=20170623T212624Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJRYRXRSVGNKPKO5A/20170623/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=e07ad853543fdea2e8fd453428ce9473079819c918c2cbbbfe216855bdcc87cc

commented

GH token isn't missing - pulp always prints that message in pulp login - if the login failed there'd be another error.

It seems travis is doing something weird now though, as lately I've had to push a bunch of updates manually thanks to

  • ERROR: Your git working tree is dirty. Please commit or stash your changes first.

(That's the actual problem here)

commented

Dirty tree could be generated package-lock.json?

commented

Yeah, that's the one. I've been fixing it in all the repos I remember to do so when making new releases (by ignoring the lockfile rather than adding it - we don't need to pin down the dev dependencies that much).