From d01741f56d2f636575d57db70c3b26e0a6a2a267 Mon Sep 17 00:00:00 2001 From: Jase Languasco Date: Fri, 9 Aug 2019 11:54:06 -0400 Subject: [PATCH] fixing a small typo --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index a8431f4..6a80bcd 100644 --- a/index.html +++ b/index.html @@ -93,7 +93,7 @@

Another big difference from git-flow is that we push to named branches on the server constantly. Since the only thing we really have to worry about is master from a deployment standpoint, pushing to the server doesn't mess anyone up or confuse things - everything that is not master is simply something being worked on.

-

It also make sure that our work is always backed up in case of laptop loss or hard drive failure. More importantly, it puts everyone in constant communication. A simple 'git fetch' will basically give you a TODO list of what every is currently working on.

+

It also make sure that our work is always backed up in case of laptop loss or hard drive failure. More importantly, it puts everyone in constant communication. A simple 'git fetch' will basically give you a TODO list of what everyone is currently working on.

$ git fetch
 remote: Counting objects: 3032, done.