search

gushphp / gush

Project Maintenance & Contributing Automation
MIT License
287 stars 43 forks source link

Auto-push before pull request creation #265

Closed aik099 closed 10 years ago

aik099 commented 10 years ago

We should automatically run "branch:fork" (only when fork is missing) and "branch:push" (when not pushed at all or remote branch outdated) commands before the "pull-request:create" command automatically. Without this after filling 9 y/n for PR message I end up having nasty exception: gush_pullrequest_create

cordoval commented 10 years ago

This is oke, the solution we are thinking is to leave gush with atomic commands but cover this with bldr-io/gush-block which is being implemented, so that this mistakes do not happen. The autopush could be but i think that checking will make this command slower, i think within the flow you need to get accustomed to:

gush i:create; gush i:take 12; git add .; gush commit -am "some change"; gush b:p; gush p:create -issue=12; gush p:merge 12; gush b:d; git checkout master; gush b:s; git branch -d 12-...

All of this will come with bldr-io/gush-block

aik099 commented 10 years ago

Or maybe have a dedicated commands, like gh (see http://youtu.be/qlrwfOL0230?t=13m4s) to allow magic PR merging and squashing at same time, like @fabpot does.

cordoval commented 10 years ago

we need categorization and run semver depending on a map for it. Dedicated commands are good too but they are composition as I am saying of minor commands.