Closed bbatliner closed 7 years ago
Done.
Brendan,
The way I recommend to create releases is to install the "hub" extension to "git" made by Github:
It adds several useful Github specific subcommands to git. In this case, the interesting one is "git release". So you can do
git release v3.1.0
Other useful extensions include "git fork" and "git pull-request". I make a lot of open source contributions on Github and find those useful.
On Tue, Jan 31, 2017 at 7:01 PM, Adam Schwartz notifications@github.com wrote:
Closed #203 https://github.com/HubSpot/vex/issues/203.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HubSpot/vex/issues/203#event-944018369, or mute the thread https://github.com/notifications/unsubscribe-auth/AABk5XHeLVB9kJG_mu7VvvCD9SRVe8E1ks5rX8tOgaJpZM4LzUjz .
-- Mark Stosberg Senior Systems Engineer RideAmigos
We've just merged in a few PRs and addressed the
./dist
folder issue from a few previous PRs.I don't have publish permissions to npm or bower. I think a GitHub release should also be made (how do I do that?). If I recall, @adamschwartz or @geekjuice did this for 3.0.0, so would you mind publishing or giving me permissions?
@markstos Your
prepublish
hook worked.grunt
ran when I tried tonpm publish
.