Capistrano 2 -> 3 git deployment differences?

In my previous capistrano version 2 deployment of an app, I always got access to git on the deployed side with .git present. This was handy when in a pinch we need to make a couple of tweaks server side and push them back to version control.

Now that we’re moving to capistrano version 3 we’ve been missing the .git folder and obviously no longer can issue git status, etc. on this deployment.

  • Amazon EC2 + Capistrano + Git: Permission denied (publickey)
  • tags vs branches in git
  • Rails Capistrano - SSHKit::Command::Failed: bundle exit status: 16
  • On this workflow, does git command needs to be installed on the production server?
  • What are Jenkins best practices with building with Grunt and deploying with Capistrano?
  • Trouble using capistrano 3 while deploying
  • Is there an option I’m missing that has changed the functionality of cap 3 that removes git vs from a project upon deployment?

    It does indeed USE git for each deployment, but it’s obviously doing something after the deploy to remove .git, etc.

  • Dockerfile strategies for Git
  • What is the difference between push branch and merge to master then push?
  • jenkins cant pull from git repository using windows batch command
  • how to redirect a git-server address?
  • Rails : why is there .keep file in every directory
  • Two-step git import over ssh
  • One Solution collect form web for “Capistrano 2 -> 3 git deployment differences?”

    You can find the .git directory in #{repo_path} variable.

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