The following instructions describe how to create a Git source code repository in the student.cs computing environment.
We will be using Mason GitLab for the rest of our CS 675 labs (i.e., Lab 1 and Lab 2). The URL for the lab GitLab repository is https://git.gmu.edu/cs675-spring20-labs.
NOTE: Don’t clone the git repo directly; instead, as described in the GitLab Setup instructions below, first fork that repo into your own private repo on our Mason GitLab server, then clone from there. You’ll commit you changes locally and push them to your private GitLab repo for grading.
First, you will need to login to GitLab by clicking
Sign in with: GMU Login. Username and Password never work
for some reason.
Important:
For both Lab 1 and Lab 2, make sure you fork
the original project GitLab repositories and then change the permission
of the project to Private.
After the repository has been forked, go to your forked project, from
Settings, go to General, from there change Visibility level to
Private.
Before cloning your GitLab repo to your student.cs computing environment, you will need to first create an RSA SSH key by typing:
% ssh-keygen -t rsa -C "your_email_addr"
Or you can simply follow this tutorial.
Then, add an SSH key to your GitLab account by following these instructions.
Test if the SSH-based access has been successfully set.
Click on the Clone button at the right-top corner of your GitLab repo’s webpage,
copy the string under Clone with SSH to clipboard.
Then, create a new directory called cs675-spring20-labs under $HOME/go/src directory
(of your Linux machine, or an EC2 virtual machine box, or whatever you have),
cd to your working directory where you are supposed to put your os161 source code,
and clone your created GitLab repo on to your server:
% cd
% mkdir -p go/src/cs675-spring20-labs
% cd go/src/cs675-spring20-labs
% git clone git@git.gmu.edu:cs675-spring20-labs/lab1.git
Now, check in the source code which you have already modified: Git allows you to keep track of the changes you make to the code. For example, if you want to checkpoint your progress, you can commit your changes by running:
% git add *
% git commit -m 'partial solution to lab 1'
% git push
You should do this early and often!
If you are checking in for the first time on an empty repo (which is your case here),
you should run:
% git push -u origin master
Please let me (the instructor) know that you’ve gotten this far in the lab, by pushing a tag to GitLab.
$ git tag -a -m "i got git and cloned the labs" gotgit
$ git push origin gotgit
As you complete parts of the labs (and begin future labs), it is a good practice to push tags. You should also be committing and pushing your progress regularly.
There are many commonly used tools in the Go ecosystem. The three most useful starting out are: Go fmt and Go vet, which are built-ins, and Golint.
For those of you in touch with your systems side (this is Distributed Systems, after all), there are quite a few resources for Go development in both emacs (additional information available here) and vim (additional resources here).
All of the code you turn in for this course should have good style. Make sure that your code has proper indentation, descriptive comments, and a comment header at the beginning of each file, which includes your name, userid, and a description of the file.
It is recommended to use the standard tools gofmt and go vet.
You can also use the Go Checkstyle tool for
advice on how to improve your code’s style. It would also be advisable to
produce code that complies with Golint where possible.
Now it’s time to go to the lab1 folder to begin your adventure!