-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
git-flow specific hooks #60
Comments
Yeah, there definitely will be hooks for many actions, but I think I'll reserve them for the rewrite. I don't want to add too many things now that will change with the next major release again. There should be hooks for before/after actions, validating, auto-bumping of version number and many a few more. |
+1 for this feature!! I would use this to upload my project to the staging server on 'git flow feature finish' and upload to the production server with 'git flow release finish' |
+1 |
+1 more! Is this still on your radar? |
Yeah! I was just having some devs complain the other day that they wish calling "git flow release 1.0.25" would automatically update the version in their package.json for them because it's a release chore. :) |
Please check #171 (comment) as there is a fork available with hooks implementation. It's a work in progress so I need people to test the living daylights out the fork. |
good idea! +1 |
Have you considered adding hooks for git-flow?
ie,
flow-{action} [start|finish]
- Invoked when {action} is started/finished would be ideal for integrating with an issue tracker to mark a feature/hotfix/etc as assigned/closed.The text was updated successfully, but these errors were encountered: