Giters

drewdeponte / git-ps

Patch Stack workflow CLI extension for Git

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

No longer force push to origin/master as part of the publish command

drewdeponte opened this issue · comments

commented

I noticed that currently we have publish doing a force push to origin/master and this seemed unsafe. It seems like if someone else has published chages to origin/master in-between the process of running of the publish command running it would result in use changing history of the remote. Even though this is unlikely that this happen in that small window of time I still think we should make sure we can't change the remotes history.

commented

So the conclusion is NO we shouldn't be doing a force push.

commented

I dog into this and it is actually using force push in the correct place to push the rr branch up to the remote, and then using NON force push to publish the patch up to origin/master.

Therefore, I am closing this bug and marketing it won't fix because there is nothing to do as it is actually correct.