Commit to develop branch directly in Git Flow?

I’m currently migrating a project to Git Flow and I’m really appreciated the flexibility it provides.

The problem is, in the following situations, may I working on and commit to a development branch directly?

  • Git commit against tag with no branch
  • How-to git backport (rebase/cherry-pick) an already merged branch
  • Commit select changes to another branch then resume work on current branch?
  • Showing git branch in shell prompt?
  • How to REALLY delete a git branch (i.e. remove all of its objects/commits)?
  • Git: Commit stopped by other branch being behind
    • a minor typo fix,
    • or a small method-level refactor,
    • or some errors fixes after a feature was merged.

    I’ve read the creator’s post and there is no mention of this situation. What you guys doing in real world?

  • Git: Why can't I see another “branch” of the commit tree?
  • Visual Studio 2013 git, only Master branch listed
  • How do I export a specific commit with git-archive?
  • Delete unpushed git commits, but keep all local work
  • ubuntu git init permission denied
  • Jenkins Multibranch Pipelines - Configuring properties in branches?
  • 2 Solutions collect form web for “Commit to develop branch directly in Git Flow?”

    I think this is up to you. What we’ve done in our project is try and have everything on a branch and then when we are about to release, merge what we definitely want in the release back to develop. Then we create our release branch from develop. I say we have done everything on a branch but for typos and very minor fixes we dont tend to create a branch.

    Totally. The benefit of isolated feature branches in git flow is primarily for the people who requested them. As long as it is a code change that you are sure is ok to go into the next release, it can be made directly into develop. You don’t want to bog down your team with too many feature branches if you can help it.

    Git Baby is a git and github fan, let's start git clone.