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
Release doesn't push tags by default #79
Comments
+1 |
2 similar comments
+1 |
+1 |
+1 and even propagate the tag to the develop branch so that |
+1 |
1 similar comment
+1 |
This is implemented in my fork git-flow (AVH Edition) |
@petervanderdoes Have you made a pull request to the original git-flow repo? |
My fork has diverged to much to make the pull request an easy implementation. I have implemented the request hooks and filters #171, which still is an open request after 10 months, and this spun off several other implementations and improvements on the original. |
+1 |
+1 - seems like an obvious thing to do as part of the workflow |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
seriously, is that still a missing feature?! |
+1 |
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. |
Yes, thank you. I managed to find your fork just after pushing for this. We're happy using your fork at work as well. Thank you very much for your effort! |
+1 |
5 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
I created a pull request addressing this issue (see #387). This is also one of the modifications I made to the ITM Gitflow fork a while ago. I'm currently setting up a proper GitHub presence for the ITM Gitflow script package. Should be ready in a few days, so that you will find detailed information on the improvements and additional features over there. |
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. |
+1, really annoying to find out two days later that the release tags you created were never pushed and everybody else is now assuming a wrong version tag. |
+1 Is there any reason for not doing this? |
+1, please |
+1 please, please! |
👍 |
This is implemented in my fork git-flow (AVH Edition) Debian and Ubuntu both, have switched to my fork for the package git-flow. Checkout the changelog for more information about bugfixes and new features implemented in my fork. |
this issues persists. It would be interesting if there was a concrete resolution. |
When doing git flow release finish 'version', git flow should push the version tag by default.
The text was updated successfully, but these errors were encountered: