Cannot lint tag commits: unknown revision or path not in the working tree

[kumar303]

Whenever TravisCI builds a tag, conventional-changelog-lint fails. It is working fine when TravisCI builds a pull request (in a branch).

Any ideas? Is my lint command wrong? The command is:

conventional-changelog-lint --from master

• Node version: v4.4.7
• npm version: 3.10.3
• conventional-changelog-lint version: 1.0.0

Example of a TravisCI failure: https://travis-ci.org/mozilla/sign-addon/jobs/143130310

Complete error:

/home/travis/build/mozilla/sign-addon/node_modules/conventional-changelog-lint/distribution/cli.js:163
    throw error;
    ^
Error: fatal: ambiguous argument 'master..HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
    at DestroyableTransform._transform (/home/travis/build/mozilla/sign-addon/node_modules/conventional-changelog-lint/node_modules/git-raw-commits/index.js:54:30)
    at DestroyableTransform.Transform._read (/home/travis/build/mozilla/sign-addon/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:159:10)
    at DestroyableTransform.Transform._write (/home/travis/build/mozilla/sign-addon/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:147:83)
    at doWrite (/home/travis/build/mozilla/sign-addon/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:313:64)
    at writeOrBuffer (/home/travis/build/mozilla/sign-addon/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:302:5)
    at DestroyableTransform.Writable.write (/home/travis/build/mozilla/sign-addon/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:241:11)
    at Socket.ondata (_stream_readable.js:542:20)
    at emitOne (events.js:82:20)
    at Socket.emit (events.js:169:7)
    at readableAddChunk (_stream_readable.js:153:18)

[kumar303]

If I check out a tag in my local repo I cannot reproduce the error. I'm not sure exactly how TravisCI is checking out the tag.

[kumar303]

Oh, huh, I guess this is happening on some branch commits too. Example: https://travis-ci.org/mozilla/web-ext/jobs/143135532 Most pull requests seem to be fine though.

[kumar303]

I see what's happening. TravisCI does a shallow clone, something like this (depending on pull request and repo):

git clone --depth=50 --branch=greenkeeper-sign-addon-0.1.0 https://github.com/mozilla/web-ext.git mozilla-web-ext

This does not fetch the master branch. I fixed it by running this before installation (in my .travis.yml):

git remote set-branches origin master && git fetch

[marionebl]

@kumar303 Thanks for reporting! Glad you solved the problem 🚀 – I created a followup issue at #7 anyway.