Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Travis CI errors "Please commit your changes or stash them before you merge." #117

Open
Jomik opened this issue Feb 20, 2018 · 1 comment

Comments

@Jomik
Copy link

Jomik commented Feb 20, 2018

Jomik/cerberus#4

https://travis-ci.org/Jomik/cerberus/builds/343590621

@ComFreek
Copy link

I have just had the same error on a PR from Greenkeeper. Removing empty lines in package.json resolved the problem, for example:

"exclude": [
  "**/node_modules/**",
  "coverage/**",

  "**/*.common-spec.{js|ts}",
  "**/*.spec.{js|ts}",

  "**/*.d.ts",
]

I debugged it with:

# .travis.yml
before_script: greenkeeper-lockfile-update
script: npm test
after_script:
  - git diff --color | cat
  - greenkeeper-lockfile-upload

The git diff showed two removed (empty!) lines in package.json. Indeed, I had two empty lines in there. It seems that during some process (not sure if it is really greenkeeper-lockfile-update) the content of package.json gets completely rewritten, but with a possibly different formatting.

ComFreek added a commit to ComFreek/async-playground that referenced this issue Mar 23, 2018
It seems the last Greenkeeper update (PR) had not committed a new
package-lock.json file. That might happened because the first Travis CI
build for the PR errored (due to
greenkeeperio/greenkeeper-lockfile#117).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants