Perfecting the deploy:update

[tamagokun]

A few scenarios to discuss to try and perfect the update command:

Currently, the command is something along the lines of:

git reset --hard --quiet && git checkout branch --quiet && git pull --quiet

depending upon whether or not you specify a branch or revision.

Here is where some issues start to arise:

• You are deploying some code that is on a new remote branch that hasn't been fetched yet. update will fail because it can't checkout a branch it doesn't know about. The same would go for tags and commit SHAs.
• You specify your branch as remote/branch_name. This will move HEAD to a remote branch rather than a local branch and git pull will fail since you can't merge into a remote branch.

@leopoiroux does this make sense? I think it may be best to go back to using git fetch, but incorporate your additional checks for branch/revision.

Something like:

for branches:

git fetch --all --quiet && git reset --hard --quiet && git checkout branch --quiet

for revisions/versions:

git fetch --all --quiet && get reset --hard --quiet revision