Closed emilsoman closed 11 years ago
@technicalpickles , what do you think ? Should be able to close #207 if this goes in.
Good use of rake args! My only concern would having it be multiple un-named arguments. I feel like I'd have to look up the correct order every time, and even then would probably make mistakes still.
Good point. How about using ENV, that would let us do something like rake release REMOTE=origin LOCAL_BRANCH=branch REMOTE_BRANCH=branch
?
Good idea! I may want to use same branch name for local and remote branch like rake release BRANCH=v3
.
@muratayusuke , done
@emilsoman yeah, that would definitely address the issue :+1:
:+1:
rake release
accepts remote(default:origin
), local branch (default:master
) and remote branch(default:master
)as optional arguments.This will tag and push the commits on your local branch named
critical-security-fix
to branch namedv3
in remote namedupstream
(if you have commit rights onupstream
) and release the gem. This is useful in scenarios where releases keep happening from older version branches, like in Rails.