Is there a way to make git flow show the commands it is executing behind the scenes?

Is there any way to make git-flow tell me ahead of time the exact git commands it will execute when I do a flow command; or tell me as it is dong it?

All i can see the output and a summary?

  • git-svn package not found for RHEL.6 linux server
  • git fast-export format and spaces
  • Sharing python modules between applications with git sub modules or svn:externals
  • Change Avatar Next to GitHub Username (For Commits)
  • Why does git diff on Windows warn that the “terminal is not fully functional”?
  • Which will get Priority between “github pages” and “directory kept at root” in case of name conflicts and why
  • Is it possible to revert a commit through GitHub's web interface
  • Can I delete my local .git repo?
  • Can't get git-tfs to clone for me
  • Git Interactive Rebase - Order of commits and which to pick/squash
  • Going back to a previous commit in Gitkraken
  • GIT: cannot push to origin/master
  • 4 Solutions collect form web for “Is there a way to make git flow show the commands it is executing behind the scenes?”

    You can use Git’s GIT_TRACE environment variable to get a detailed trace of commands executed. For example:

    GIT_TRACE=true git flow feature start bar
    

    … displays …

    trace: exec: 'git-flow' 'feature' 'start' 'bar'
    trace: run_command: 'git-flow' 'feature' 'start' 'bar'
    trace: built-in: git 'config' '--get' 'gitflow.branch.master'
    trace: built-in: git 'branch' '--no-color'
    trace: built-in: git 'config' '--get' 'gitflow.branch.develop'
    trace: built-in: git 'branch' '--no-color'
    trace: built-in: git 'config' '--get' 'gitflow.branch.master'
    trace: built-in: git 'config' '--get' 'gitflow.branch.develop'
    trace: built-in: git 'config' '--get' 'gitflow.branch.master'
    trace: built-in: git 'config' '--get' 'gitflow.branch.develop'
    trace: built-in: git 'config' '--get' 'gitflow.origin'
    trace: built-in: git 'config' '--get' 'gitflow.prefix.feature'
    trace: built-in: git 'branch' '--no-color'
    trace: built-in: git 'branch' '-r' '--no-color'
    trace: built-in: git 'branch' '--no-color'
    trace: built-in: git 'branch' '-r' '--no-color'
    trace: built-in: git 'checkout' '-b' 'feature/bar' 'develop'
    Switched to a new branch 'feature/bar'
    
    Summary of actions:
    - A new branch 'feature/bar' was created, based on 'develop'
    - You are now on branch 'feature/bar'
    
    Now, start committing on your feature. When done, use:
    
         git flow feature finish bar
    

    If you want more details than that, you can use the sh shell xtrace option:

    After expanding each simple command, for command, case command, select command, or arithmetic for command, display the expanded value of PS4, followed by the command and its expanded arguments or associated word list.

    Edit the git-flow script and add set -x right after the #!/bin/sh first line. Executing the above command, git flow feature start bar, would display a lot of information (more than can be included in an answer).

    Some commands have a verbose flag, but I believe the answer to your question is “No”.

    You can see what each command does by checking the source. It’s well documented so you can understand what is happening even without knowing bash.

    Actually, after checking the source, there indeed seems to be a way to log the commands git flow uses internally; at least most of them. The functionality was introduced with this commit and hints of a show_commands setting. You should be able to enable it using --show_commands, and it will print out most git commands it uses internally.

    Use the --showcommands switch, for instance:

    git flow feature start FEATURENAME --showcommands
    
    Git Baby is a git and github fan, let's start git clone.