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.

  • Git error: “fatal: .. does not appear to be a git repository” - when deploying via Capistrano
  • Capistrano Deploy (cap deploy) failing, Authentication errors
  • Ignoring certain files and changes in capistrano's current directory for development environment
  • tags vs branches in git
  • How do I minify my source code before deployment
  • Capistrano Many Private Repo Github
  • 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.

  • Undoing a 'git push'
  • How do I delete a Git branch with TortoiseGit
  • `composer install` for production deployments
  • Chosen plugin Options are not passed to Cloned row
  • How to push a subtree to heroku using a non master branch
  • Transfer existing website to git
  • 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.