Git push about mversion HOT 5 CLOSED

Hi and thanks for posting an issue!

I'm fairly sure npm version doesn't push to the remote, as I've tried to mimic the usage of it. You can see the implementation here: https://github.com/npm/npm/blob/master/lib/version.js, but maybe you are thinking of grunt-bump or gulp-bump?

I have been considering adding support for pushing as well. Originally my philosophy was to not diverge too much away from npm version, but i've already done so, really.

Often while using mversion I catch myself doing:

$ mversion patch -m
$ git push && git push --tags

So doing something like

$ mversion patch -m -p

instead might be a good idea. It would have to be optional though, and not enabled by default. Also, should have that default remote is origin and branch is current branch. But allowing to override with something like

$ mversion patch -m -p upstream featureBranch

What do you think?

from mversion.

Sorry, I was confused. Of course it is npm version and it doesn't do remote pushes. Not sure what I was thinking.
Anyways, I totally agree and think that mversion patch -m -p is a fantastic idea!

from mversion.

Instead of having this as a part of the CLI, I found that it is much cleaner to use post- and preupdate hooks in a .mversionrc file.

Just create this file in your root:

.mversionrc

{
  "scripts": {
    "postupdate": "git push && git push --tags"
  }
}

This will push after the version has been bumped.

from mversion.

Nice solution. This rocks!
Extra props for letting me put that .mversionrc in my home dir.

from mversion.

All credit to @timkelty for the idea!

from mversion.