|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Yes, of course force push is really dangerous.
But in our case it's needed, for example, we are using https://gemfury.com/ service.
With this we can push code to be build directly with git: http://devcenter.gemfury.com/articles/git-push-package.html
But, as we have to always push on remote master branch, it's needed to force push.
For example:
we have 2 current branch for our software 2.4 and master (future 3.0).
we are pushing master to master for building 3.0.0-dev version and then push --force 2.4 to master for building 2.4.0-dev.
It's really awesome.
I already have a wroking branch here: https://github.com/guilhem/git-plugin/tree/forceOption
Just need to fix credentials :/ (don't know how to do...)