New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hotfixes cannot be "published" #92
Comments
Our team could also benefit from this. We work on a web based application and often need to vet hotfixes in a staging environment. While we can fairly painlessly push the hotfix branch to github, the command would be a great convenience. |
Additional to this, it would be very useful to have the track function added so that published hotfix branches can easily be brought down. This is something my team could very much do with as well. +1 |
@cranberyxl Exactly the same situation here. |
Exactly the same situation, please add such feature! |
+1 |
1 similar comment
+1 |
Really need this +1 |
This is definitely needed here. Love git flow, and I've love to see publishable hotfixes. We do this for code reviews. |
+2 :) |
+1 Trying to use post-receive hooks + CI server to automatically test hotfixes, then deploy from campfire! |
Thanks @phoet. |
Given the #163 has been merged, why this issue has not been closed? |
hoping this gets released soon! it'll be a very helpful addition. |
This is implemented in my fork git-flow (AVH Edition) Checkout the changelog for more information about bugfixes and new features implemented in my fork. |
waiting for that as well |
+1 |
1 similar comment
+1 |
Is there any development on this subject? I, too, would really like to have this feature, but the lack of input from the repo's author leads me to wonder wether it'll ever happen? |
+1 |
This works for me. Not sure if I misunderstand the issue, but with a relatively recent git flow (installed via apt-get 2 weeks ago on ubuntu 14.04) I can do
|
@emanuil-tolev because the git-flow installed via apt it's the git-flow (AVH Edition) a @petervanderdoes 's fork, not the @nvie version. |
++ ; could definitely use this! Thanks! ;) |
+1. Definitely a good idea! |
++ |
+1 but after 4 years of having this ticket opened it seems there's no hope to have it done |
Not had any problems with a year and half of https://github.com/petervanderdoes/gitflow , can recommend that fork. |
Ok, thanks @emanuil-tolev - will give that a try! ; ) |
@keithamus does 'closed' mean 'wontfix' ? |
Hey @gsaslis; I filed the issue back in 2011. I don't have any ownership of this repo. Closed means I'm no longer interested in this issue personally, and I want to clean up my issues page as it is my todo list. If you're interested in this you should maybe file the issue again? |
@keithamus oh, ok, sorry about the confusion there... : ) |
@gsaslis np. I'd say yes - looks like the fork might be the way to go. There's been no activity on this repo for years. |
This is an old thread, but I came here looking for the same solution. This repo is unchanged in 5 years and it looks like it will continue like this, I strongly suggest you to use the AVH fork, since it provides more options including If you installed git-flow using brew, you can simply change it with
|
While release and feature branches can all be published (git flow release/feature publish), hotfix branches cannot.
In our particular development environment, only senior staff can merge to master, meaning that hotfixes need to be pushed to the central repository by junior staff, so a senior member can pull that hotfix branch and then merge to master (git flow hotfix finish). The problem here is that because hotfixes cannot "publish", pushing a hotfix takes on a completely different mantra to pushing a release/feature branch (I'm telling our junior staff that for hotfixes they have to run
git push origin hotfix/1.0.1
as opposed togit flow hotfix publish
, which they are used to).So in summary. Can we get "hotfix publish" added as a command to git flow?
The text was updated successfully, but these errors were encountered: