From c40c53873b7da5423db9cc1b2453231a034b9385 Mon Sep 17 00:00:00 2001 From: Owen Jacobson Date: Thu, 19 Sep 2013 16:57:13 -0400 Subject: Missing paren (thanks, @SurprisingEdge!) --- wiki/git/stop-using-git-pull-to-deploy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'wiki/git/stop-using-git-pull-to-deploy.md') diff --git a/wiki/git/stop-using-git-pull-to-deploy.md b/wiki/git/stop-using-git-pull-to-deploy.md index 5b0f2a4..f6878fb 100644 --- a/wiki/git/stop-using-git-pull-to-deploy.md +++ b/wiki/git/stop-using-git-pull-to-deploy.md @@ -33,7 +33,7 @@ preserved (and merged) into the deployment, for example; once this happens, the actual deployed commit will _never_ match the intended commit. `git pull` will approximate the right thing "by accident": if the current -local branch (generally `master` for people using `git pull` is always clean, +local branch (generally `master`) for people using `git pull` is always clean, and always tracks the desired deployment branch, then `git pull` will update to the intended commit exactly. This is pretty fragile, though; many git commands can cause the local branch to diverge from its upstream branch, and -- cgit v1.2.3