strongloop / strong-tools

75%

master: 91%

LAST BUILD ON BRANCH shrinkwrap-release-only

branch: shrinkwrap-release-only

CHANGE BRANCH

x

Reset

• shrinkwrap-release-only
• apache
• bump-shrinkwrap-on-release
• codacy
• copyright-enhancements
• copyright-ts
• de-blip
• default-version
• dependency-updates
• expand-test-coverage
• fail-badly
• feature/improve-npmignore
• filter-shrinkwrap-resolved
• fix-shrinkwrap
• fix-styleguide-urls-1468452411653
• master
• ref/use-strict
• tap-tests
• test-all-the-things
• testing-codacy
• typo
• unruby
• update/dependency-lodash
• v4.4.0
• v4.5.0
• v4.5.1
• v4.5.2
• v5.0.0
• v5.1.0
• v5.2.0

Build # 36

Build Type

push

travis-ci

Committed by rmg

Commit Message

slt-release: commit shrinkwrap, but don't merge it

If there is an npm-shrinkwrap.json file present AND that file has not
been committed to the current branch, then commit it as part of the
release tag but filter it out of the actual merge back in to the base
branch.

Note that this mode is NOT triggered if npm-shrinkwrap.json is already
part of git. If you want to enable that style of development going
forward, you will have to commit it separately _before_ running
`slt-release`, otherwise it will be ignored and filtered out.

This is done using some slightly low-level git operations to manually
compose a merge commit in a way that neither 'git merge' or 'git commit'
interfaces allow. At least it is well commented!

Run Details

418 of 561 relevant lines covered (74.51%)

25.51 hits per line