simon/semantic-release
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

style: update to prettier@1.9.0

Browse Source
This commit is contained in:
Pierre Vanduynslager 2017-12-05 09:51:15 -05:00
parent f30fb6c8af
commit 0761ef378a
2 changed files with 4 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
lib/get-commits.js
View File

@ -84,24 +84,18 @@ function noGitHeadMessage(branch, version) {
This means semantic-release can not extract the commits between now and then. This means semantic-release can not extract the commits between now and then.
This is usually caused by releasing from outside the repository directory or with innaccessible git metadata. This is usually caused by releasing from outside the repository directory or with innaccessible git metadata.
You can recover from this error by creating a tag for the version "${ You can recover from this error by creating a tag for the version "${version}" on the commit corresponding to this release:
version
}" on the commit corresponding to this release:
$ git tag -f v${version} <commit sha1 corresponding to last release> $ git tag -f v${version} <commit sha1 corresponding to last release>
$ git push -f --tags origin ${branch} $ git push -f --tags origin ${branch}
`; `;
} }
function notInHistoryMessage(gitHead, branch, version) { function notInHistoryMessage(gitHead, branch, version) {
return `The commit the last release of this package was derived from is not in the direct history of the "${ return `The commit the last release of this package was derived from is not in the direct history of the "${branch}" branch.
branch
}" branch.
This means semantic-release can not extract the commits between now and then. This means semantic-release can not extract the commits between now and then.
This is usually caused by force pushing, releasing from an unrelated branch, or using an already existing package name. This is usually caused by force pushing, releasing from an unrelated branch, or using an already existing package name.
You can recover from this error by restoring the commit "${gitHead}" or by creating a tag for the version "${ You can recover from this error by restoring the commit "${gitHead}" or by creating a tag for the version "${version}" on the commit corresponding to this release:
version
}" on the commit corresponding to this release:
$ git tag -f v${version || '<version>'} <commit sha1 corresponding to last release> $ git tag -f v${version || '<version>'} <commit sha1 corresponding to last release>
$ git push -f --tags origin ${branch} $ git push -f --tags origin ${branch}
`; `;

4
test/integration.test.js
View File

@ -492,9 +492,7 @@ test.serial('Create a tag as a recovery solution for "ENOTINHISTORY" error', asy
t.regex( t.regex(
stderr, stderr,
new RegExp( new RegExp(
`You can recover from this error by restoring the commit "${head}" or by creating a tag for the version "${ `You can recover from this error by restoring the commit "${head}" or by creating a tag for the version "${version}" on the commit corresponding to this release`
version
}" on the commit corresponding to this release`
) )
); );