git-flow release checkout and pull

[kenfodder]

This might be a stupid question, a release is very similar to a feature branch, why can one publish a release and then can't pull using git-flow commands like you can in a feature branch? Or does it just need implementing?

Thanks.

[Zoramite]

The git flow release finish creates a tag as part of the process. If you do a git push --tags it will push that tag out to the remote repository. In that way a git pull or git fetch will retrieve the tags from the remote repository so there really isn't any need to have a git flow specific process for that. There is an issue to add automatic push in #79

[woodyrew]

@Zoramite the git flow release finish command will merge the release branch into master and delete the branch. I don't think that's the problem.

Take the following workflow as an example:

• Bill runs git flow release start v1.0 to start hardening the release candidate.
• Bill then pushes the release to the central repo with git flow release publish v1.0 so other developers can work on the branch.
• Jane needs to work on it so she expects to run git flow release pull v1.0 but has to do:
  • git fetch origin release/v1.0
  • git branch –no-track release/v1.0 FETCH_HEAD
  • git checkout release/v1.0

[xak2000]

Usually I do just:

$ git checkout release/v1.0
Branch release/v1.0 set up to track remote branch release/v1.0 from origin by rebasing.
Switched to a new branch 'release/v1.0'

But it will be convinient to have separate git-flow command to pull unfinished release branch.