GitHub tarball links make it easy to reference unreleased commits and branches in dependencies from another project's package.json file, but these links don't work for private projects.
Can npm-internal help publish devbuilds? Instead of refusing to publish npm-internal could publish a package named based on the output of git describe.
The output looks like v0.8.0-161-g8685bfe, where v0.8.0 is the latest tag, 161 is the number of commits since the tag, and g8685bfe is the partial SHA of the current commit. Running git describe with the tag checked out will simply return v0.8.0.
GitHub tarball links make it easy to reference unreleased commits and branches in dependencies from another project's package.json file, but these links don't work for private projects.
Can npm-internal help publish devbuilds? Instead of refusing to publish npm-internal could publish a package named based on the output of
git describe.The output looks like
v0.8.0-161-g8685bfe, wherev0.8.0is the latest tag,161is the number of commits since the tag, andg8685bfeis the partial SHA of the current commit. Runninggit describewith the tag checked out will simply returnv0.8.0./cc @GretaCB @lbud