# move to the correct directory; 
# there should be a directory in your
# top directory called csci260.  Change into ("cd") that directory
# Note: if this is too verbose for you, you can look at gitShort.txt

cd csci260

# Note: git repository csci260/LabX belongs to GARA
# You will not be allowed to push to GARA's repository.
# Therefore you must fork GARA's repository to one that is YOURS.
# You do that this way.  (Recall: for Linux, $USER is a way of 
# identifying YOU.)  Type it just as below, except give the 
# actual name of the lab -- i.e., instead of LabX, write Lab2, or Lab3, or 
# whatever...

ssh csci fork csci260/LabX csci260/$USER/LabX

# now you have a server-side repository just for you.  With the 
# next command, you will clone it, creating a git-enabled directory 
# that is a subdirectory of the one you are currently in.
# You will be able to work on code in that directory.
# Note that if you clone GARA's directory instead (i.e., if you leave
# out $USER), you won't be able to push back to the repository 
# linked to the directory thus created!

git clone csci:csci260/$USER/LabX

# cd into the directory, and find out what goodies GARA has 
# given you for this lab!

cd LabX

# edit the files, compile, test them, debug, etc.  When they are
# ready to submit, before the deadline, while in this directory, 
# do the following:

git add .
git commit -m "Your comments, such as Merge does not work correctly"
git push

# The push command pushes the files in this directory that have been 
# "added" (you added all of them using the "add ." command) to 
# the repository that is linked to this directory -- i.e., the one
# you cloned.  If you cloned a repository belonging to GARA -- 
# bad news!  You won't be able to push to it, because GARA owns it, 
# not you!  Jim has a way of fixing this, i.e., setting the directory to 
# point to YOUR git repository instead of GARA's -- go to his web page 
# on the subject.